-
Notifications
You must be signed in to change notification settings - Fork 360
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
Configurable docker push timeout #711
Comments
I succeed in reproducing the error locally. When we create a docker Documentation say :
I let you now if changing this parameter fix the issue. |
Indeed increasing that timeout fixed the issue. The line of code is that one It needs to be changed to something like that : client = docker.APIClient(version="auto", timeout=CHOSEN_TIMEOUT, **kwargs_from_env()) Maybe this would be great to make it configurable. In this initial command line (like |
Or by changing the What do you think ? |
Taking it from the environment sounds like a good idea to me. Mostly because we have a huge number of CLI flags already :-/ and my guess is this would be mostly used by deployments like BinderHub and not humans. I think |
agree
Indeed, I didn't saw that it was from I'll then write my own function to get this parameter from env variables. |
Something like this sounds like a good idea or maybe we can contribute to docker-py to get
|
Puts it in the ContainerEngine interface specific to Docker, so PodMan can implement its own when necessary. Fixes jupyterhub#711
via https://discourse.jupyter.org/t/i-get-read-timed-out-errors-on-when-pushing-image-ovh/1394/7?u=betatim
Is there a way we can control/increase the timeout for the push operation at the end of the build? We are getting timeouts for this step on the OVH deployment and a potential way to help here is to increase (or make configurable) the push timeout.
The first step here is to find out how to control the timeout in the docker python client library we use.
The text was updated successfully, but these errors were encountered: