readthedocs.org: New Docker client returning timeout on EXEC
https://sentry.io/read-the-docs/readthedocs-org/issues/533022676/
timeout: timed out
(10 additional frame(s) were not displayed)
...
File "readthedocs/doc_builder/environments.py", line 472, in run
return super(BuildEnvironment, self).run(*cmd, **kwargs)
File "readthedocs/doc_builder/environments.py", line 307, in run
return self.run_command_class(cls=self.command_class, cmd=cmd, **kwargs)
File "readthedocs/doc_builder/environments.py", line 478, in run_command_class
return super(BuildEnvironment, self).run_command_class(*cmd, **kwargs)
File "readthedocs/doc_builder/environments.py", line 346, in run_command_class
build_cmd.run()
File "readthedocs/doc_builder/environments.py", line 234, in run
output = client.exec_start(exec_id=exec_cmd['Id'], stream=False)
(Build) [astropy:latest] timed out
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17 (12 by maintainers)
I just manually upgraded
docker
in ourbuild03
to version3.7.2
and triggered a couple of builds: they passed. Also, Sentry does not report any problem on build03 at the moment.I think we can test this for some days more and then upgrade our requirements file to make this change in all of our builders.
Just deployed and the issue is still present in 3.3.0 😦
I downgraded it to 3.1.3 again.
@stsewd we don’t know yet. That PR wasn’t deployed yet.
A new docker version was released today: https://github.com/docker/docker-py/releases/tag/3.3.0
It says it fixes an issue with the timeout for
stop
andrestart
. It may be related with our case…