We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
New! It is now possible to set a container's HostConfig when creating a container. Previously this was only available when starting a container.
See https://docs.docker.com/reference/api/docker_remote_api/#v115
So it would be useful if Client.create_container could accept all the HostConfig related parameters that are currently accepted by Client.start.
Client.create_container
HostConfig
Client.start
Meanwhile, we can construct a config dictionary and supply that to Client.create_container_from_config.
Client.create_container_from_config
Also note:
New! Passing the container's HostConfig on start is now deprecated. You should set this when creating the container.
So there should probably be a deprecation warning when those parameters are supplied to start
start
But that's probably a separate issue.
The text was updated successfully, but these errors were encountered:
+1, this would mitigate #419
Sorry, something went wrong.
Fixed by #428 !
No branches or pull requests
See https://docs.docker.com/reference/api/docker_remote_api/#v115
So it would be useful if
Client.create_container
could accept all theHostConfig
related parameters that are currently accepted byClient.start
.Meanwhile, we can construct a config dictionary and supply that to
Client.create_container_from_config
.Also note:
So there should probably be a deprecation warning when those parameters are supplied to
start
But that's probably a separate issue.
The text was updated successfully, but these errors were encountered: