Mis-tagged docker images

[ghost]

I am attempting to set up a test VM for Docker and running into an issue while running first_build.sh. The various docker images (combine-docker_mysql, combine-docker_django, etc) are being tagged as combinedocker_<> instead. This results in an "image not found" error when it tries to build a container on these images. I've had to go through and retag each image and everything completes correctly but I've been unable to track down the source of the mistag (I'm familiar with Docker but fairly new to docker-compose)

[ghost]

I was able to replicate this in a fresh VM instance. Screenshot shows the expected repository name and images created during first_build.sh.

[antmoth]

This is caused by a change in docker-compose across versions. The dev branch of this repo is basically stable and I should probably merge it into master, as it fixes this and several other issues.

[ghost]

I'll wait for the merge and then test. I tried pulling the dev branch and working with that but ran into a some issues.

[antmoth]

Should be fixed in v0.11. @wastatelibrary still having issues?

[ghost]

Unfortunately, I don’t have access to some of my resources to test this at the moment. I will confirm as soon as I am able.

[ghost]

Getting Service 'combine-celery' failed to build: pull access denied for combine-docker_combine-django. I'm looking into it to see if it's a config error (freshly spun up VM)

[ghost]

It appears that there's still hyphens in ./combine/Dockerfile and ./celery/Dockerfile causing issues. Additionally, it looks like it's trying to build combine-celery before building the base combine-django image. Editing the above Dockerfiles and manually building the combine-django image leads me to the following error:

Step 8/22: COPY combine/combine /opt/combine/
COPY failed: stat /var/snap/docker/common/var-lib-docker/tmp/docker-builder172438767/combine/combine: no such file or directory

Is something not mounting like it should?

[antmoth]

Is the user that you're running docker-compose as in the docker user group? That 'pull access denied' error looks like it might point at needing to be in the docker group.

[ghost]

Confirmed group membership, logged out and back in, still receive error. Rebooted, still receive error.