-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
proposal: Add option to pull base images #8886
Comments
There are a couple of problems which trigger continuous rebuild of the containers which have difficult solutions, this option enables a workaround. docker/docs#8886
There are a couple of problems which trigger continuous rebuild of the containers which have difficult solutions, this option enables a workaround. docker/docs#8886
There are a couple of problems which trigger continuous rebuild of the containers which have difficult solutions, this option enables a workaround. docker/docs#8886
Thank you for your feedback. This seems to be a feature request or a fundamental change in the way Docker works, but this GitHub repository is only for Docker documentation. Please file an issue in https://github.com/docker/ instead. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Problem description
When using a base image and --cache-from to avoid rebuilding containers in CI environments for example, if the base image used in the dockerfile is stale, it triggers a rebuild of the container. This is not the case when the base images are pulled.
Ideally there would be a way to pull a container and it's base images so they are all updated.
For example, see the use of --cache-from in our CI for MXNet here:
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-cpu/branches/master/runs/707/nodes/49/steps/176/log/?start=0
Problem location
I saw a problem on the following URL:
I couldn't find the information I wanted. I expected to find it near the following URL:
Other:
Project version(s) affected
Suggestions for a fix
See above.
The text was updated successfully, but these errors were encountered: