-
Notifications
You must be signed in to change notification settings - Fork 21
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
(fix) reuse dockerfile since it gets cacheds and reused anyway in my … #604
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this solves #603 : I deleted all the containers, images and volumes from my machine and could still run docker compose up
without building and without docker attempting to pull the image.
What command did you run when getting the errors?
If these changes don't solve #603 , I would keep the reference to the image as it makes clear that all 3 containers use the same image and makes sure that they stay the same.
The thing is: it works but docker still throws the errors. I would still not simply ignore it. $ docker --version |
With this changes the errors don't appear. |
When you say "it works", do you mean the celery containers work too or just the web container? |
What OS are you on? |
All containers running
on Linux Mint |
So if the error message pops and the containers still run, then the error message is wrong? That's weird. |
I think we don't need to refer to an image (which hasn't been build) according to this docker/compose#7343 (comment) and can build all