-
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
compose 1.8.2. TypeError: log_timeout_error() takes exactly 1 argument (0 given) #3783
Comments
Thanks for reporting. I've confirmed that we've got a bug in the code that handles timeouts - the fix is in #3784. As for your timeout problem, it certainly sounds like you've got a weird script. I'd recommend making it so that it execs out to the mysqld process after performing whatever setup is necessary. |
i too face same issue also how to pass -h / hostname to docker-compose |
I noticed that i have the exact same error when i use
|
Same here, and not using |
Also experiencing the same issue when something times out...
I'm using the Mac app if that makes any difference. |
Seeing the same thing as OP $ docker -v |
|
The issue just occured to me. Using:
|
I have a set of containers where the mysql one has a 'weird' shell script as entrypoint.
I can start mysql after starting the container via 'docker exec ... /etc/init.d/mysql start', but when I do so, the command line hangs (I can ctrl+c to exit the docker command, and the mysql service does indeed run).
I just updated to docker 1.12 and docker-compose 1.8.0, and it seems that now handling of the 'rogue' container is getting worse: after executing the above steps, I tried 'docker-compose ps' and I get:
the same happens if I run
docker-compose kill -s SIGKILL
The text was updated successfully, but these errors were encountered: