-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose build fails on initial install #263
Comments
I would like to work on this issue! |
The issue seems to be with a few of the Dockerfile RUN statements. After doing the initial clone with
it appears the the problems come from 3 files |
Hi @edwhardo, It could have been an issue before Can you please provide more information on your Docker/Compose installation? echo MusicBrainz Docker: `git describe --always --broken --dirty --tags`
echo Docker Compose: `docker-compose version --short` && \
sudo docker version -f 'Docker Client/Server: {{.Client.Version}}/{{.Server.Version}}' Also what is your host platform and version? lsb_release -a Please try building images with no cache as follows and provide full logs as attachments: sudo docker-compose build --no-cache Regards |
Hi @yvanzo ,
I'm running Unraid 6.12.5 with the docker-compose plugin I finally managed to get it to build by editing the Dockerfiles to change the gpg key install for nodejs and postgresql, but when I try to start it, there are permissions errors due to my OS (Unraid) not letting the entrypoint scripts run due to their location on the rootfs. I was also using when the build was successful
So, it seems that my issue now has everything to do with the idiosyncracies of my OS and chosen method of running docker-compose (as a plugin). I'll seek assistance with the author of the plugin, but it seems strange that I was having the gpp key issues. Should we close this, or would you like to see the edits I made for a successful compile? |
At least your Docker version is recent enough as I have one test VM running Docker 20.10.12 (on Ubuntu focal). Please check the base image used to build the image for the sudo docker images --filter reference=postgres Here is what I get:
Otherwise I don’t have other hint, so it might be related to your host system which I don’t know anything about. As for the GPG keys, we made changes to how these are handled just two months ago; See 4513294. Your changes shouldn’t be needed. My guess is that the root cause is more likely one the above (either the base image is not recent enough or the host system has some issue). |
That command returned nothing. The only db entry is: I've manually updated docker-compose to I'll just wipe it and start over. Its good to know that GPG stuff is sorted. Will advise if I have success. |
That’s weird. Try building with pulling the latest version of the base image as follows: sudo docker-compose build --no-cache --pull db Please share the full log, especially the Step 2/9 at the beginning. |
That built, but there were only 4 Steps.
I'm pretty new to Docker (not to Linux), and I can't work out how to see the full log. I tried I also followed the documented steps on a Ubuntu machine and it worked, so it must be my Unraid environment. I should have another machine around that has enough grunt to run musicbrainz. I think its time to go pruning the dangling images and contrainers. |
The You have to copy the output of the sudo docker-compose build --no-cache --pull db 2>&1 | tee build.db.log
It can’t hurt indeed. |
Thanks for the redirect and pipe to tee tip. |
I just noticed that all the errors are related to files being copied from the Can you please provide the output of the following added diff --git a/build/musicbrainz/Dockerfile b/build/musicbrainz/Dockerfile
index 04686425..0236e091 100644
--- a/build/musicbrainz/Dockerfile
+++ b/build/musicbrainz/Dockerfile
@@ -16,6 +16,7 @@ RUN curl -sSLO --retry 5 https://github.com/jwilder/dockerize/releases/download/
rm -f dockerize-linux-amd64-$DOCKERIZE_VERSION.tar.gz
COPY keyrings/* /etc/apt/keyrings/
+RUN ls -all /etc/apt/keyrings/ && exit 1
ARG NODE_MAJOR_VERSION=20
ARG POSTGRES_VERSION=12
SHELL ["/bin/bash", "-o", "pipefail", "-c"] |
|
this Dockerfile edit gets a lot further down the road to a successful build.
|
@yvanzo , you were certainly correct about the files not being copied with the correct permissions. I'm doing this on an Unraid server with the Docker Compose Manager Plugin. Unraid doesn't allow any exe files in /boot and plugins are installed in /boot/config/plugins Not sure why I needed to change the way the postgresql and nodejs repositories were added, but if it doesn't affect others, there isn't any reason to change it. These are the changes that I needed to get things built:
|
You might encounter similar permission issues with helper scripts under |
docker-compose build fails
14.72 Reading package lists...
15.11 W: GPG error: http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease: Unknown error executing apt-key
15.11 E: The repository 'http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease' is not signed.
failed to solve: executor failed running [/bin/bash -o pipefail -c echo "deb [signed-by=/etc/apt/keyrings/pgdg.asc] http://apt.postgresql.org/pub/repos/apt/ $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list
apt-get update
apt-get install --no-install-recommends -qy cpanminus bzip2 gettext g++ git libdb-dev libexpat1-dev libicu-dev liblocal-lib-perl libpq-dev libssl-dev libxml2-dev make nodejs pkg-config postgresql-client-${POSTGRES_VERSION} python2-minimal xz-utils zlib1g-dev && rm -rf /var/lib/apt/lists/*
corepack enable]: exit code: 100
The text was updated successfully, but these errors were encountered: