-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Build() should default to pull=False
#622
Milestone
Comments
+1 |
btw |
jpopelka
added a commit
to jpopelka/atomic-reactor
that referenced
this issue
Jun 1, 2015
…lient().build() It defaults to True (might change in future, docker/docker-py#622). Set it to False as we pull base image ourselves with InsideBuilder.pull_base_image()
jpopelka
added a commit
to jpopelka/atomic-reactor
that referenced
this issue
Jun 1, 2015
…lient().build() It defaults to True (might change in future, docker/docker-py#622). Set it to False as we pull base image ourselves with InsideBuilder.pull_base_image()
jpopelka
added a commit
to jpopelka/atomic-reactor
that referenced
this issue
Jun 2, 2015
…lient().build() It defaults to True (might change in future, docker/docker-py#622). Set it to False as we pull base image ourselves with InsideBuilder.pull_base_image()
jpopelka
added a commit
to containerbuildsystem/atomic-reactor
that referenced
this issue
Jun 2, 2015
…lient().build() It defaults to True (might change in future, docker/docker-py#622). Set it to False as we pull base image ourselves with InsideBuilder.pull_base_image()
Fixed by #624 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The default behavior of docker cli when building does not pull by default. You must provide the
--pull
flag. I suggest thatdocker-py
follows the same rule and default topull=False
https://github.com/docker/docker-py/blob/master/docker/client.py#L309
The text was updated successfully, but these errors were encountered: