-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
Connection timeout in docker slim while reducing docker image size #22
Comments
Is there more to the command or './docker-slim build --http-probe' is the whole thing? Can you also set the debug flag, so the command looks like this: './docker-slim --debug build --http-probe your_image_id_or_name_here'. What's your docker-slim version? |
sometimes the process gets stuck at |
Sometime you might see HTTP connection errors if the HTTP probe wasn't done when you press enter. That error is harmless for the most part. Either way, the master process sometimes gets stuck waiting for the temporary container to finish. It's really just stuck on the I/O waiting for the target to emit events. Need to replace the Mongos IPC library with something more reliable. It's on the official wishlist and it will be addressed soon. |
Closing this one because it's pretty old. The recent releases add a number of HTTP probing enhancements, which should address problems like this either by doing a better job retrying or detecting that the target container is down. Try the latest release when you get a chance ( https://github.com/docker-slim/docker-slim/releases/tag/1.24 ). Thanks again for reporting the problem! |
I tired to reduce my docker image size using docker slim but facing connection time out issue
i have used this command: ./docker-slim build --http-probe
but got the below error
INFO[0008] docker-slim: http probe - GET http://127.0.0.1:32792/ error: Get http://127.0.0.1:32792/: dial tcp 127.0.0.1:32792: getsockopt: connection refused
INFO[0008] docker-slim: HTTP probe done.
INFO[0270] sendCmd(): receive timeout...
Can anyone help on this ??
The text was updated successfully, but these errors were encountered: