-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
log_timeout_error() TypeError #3904
Comments
No nothing before, I run the command and then this prints out |
That means |
I've got this one too with Docker for Mac. Answers to previous questions
No, just stacktrace: $ docker-compose up
Traceback (most recent call last):
File "<string>", line 3, in <module>
File "compose/cli/main.py", line 61, in main
File "compose/cli/main.py", line 113, in perform_command
File "contextlib.py", line 35, in __exit__
File "compose/cli/errors.py", line 56, in handle_connection_errors
TypeError: log_timeout_error() takes exactly 1 argument (0 given)
docker-compose returned -1
I've tried
Happens with all compose files, not just one
No custom When it happensIt mainly happens when running a docker-compose container and then putting the computer to sleep (or closing the macbook lid). But it also happens randomly even without putting the machine to sleep. What helpsRestarting Docker for Mac doesn't help, only full reboot (which probably means that some service/daemon requires restart that I don't know). Docker versionsI'm running the latest stable version. Here's various related app versions: $ docker --version
Docker version 1.12.0, build 8eab29e
$ docker-compose --version
docker-compose version 1.8.0, build f3628c7
$ docker-machine --version
docker-machine version 0.8.0, build b85aac1 |
Hi @aripalo , thanks for the detailed report. Seeing as |
@shin- Ah true! Thanks for pointing out! I'll leave a comment there as well. I'm not that familiar with the whole Docker ecosystem so I can't really say for sure (which is probably obvious), but… I'd say this is 50%/50% The cause itself seems to be To me … but the main issue of course is that Shoutout to all you Docker org members: I've been using Docker on AWS Elastic Beanstalk for few months and now replacing local Vagrant + VirtualBox based development environments with |
@aripalo awesome to hear you've had a good experience overall, thanks for the kudos 🐱 Yeah, as far as the stacktrace is concerned, we already have a fix in master for it. See my comment above. It will be in our 1.8.1 release! |
Also anyone having that "Docker hangs" issue with But just in case someone ends up reading this thread: A temporary “solution” (until an actual fix comes along) is to run |
WIth docker (for mac) running I do "docker-compose up" and I receive this traceback.
The text was updated successfully, but these errors were encountered: