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
Running '/bin/cat /dev/zero' in a container kills Docker with 'Signal 9' #5
Comments
Couldn't reproduce it (tried If you remember how you did it and could try again, that'd be great! |
All my notes are in the issue. If you can't reproduce, it's very possible On Thu, Mar 14, 2013 at 6:00 PM, jpetazzo notifications@github.com wrote:
|
Boldly closing as "could not reproduce", then :-) |
Update events to consume the json stream and not buffer in memory
Set content-type to json on v2 registry GET manifest
Add --add-registry and --block-registry options to docker daemon
Basic simplebridge driver
Volume plugins w/ flag
WIP: support hostname
Forward-porting changes for FreeBSD on v17.05.0-ce
[18.06] bump libnetwork to 430c00a
Create the containerd image service
When I create a new container and run the command '/bin/cat /dev/zero' inside it, it runs for approximately 2-5 seconds, then Docker prints 'Signal 9' and exits.
I could reproduce this reliably with the same command, but could not reproduce it with any other command. In particular, short-lived commands (eg. '/bin/touch /foobar') run properly without crashing, as well as other long-lived commands (eg. '/bin/sleep 10').
The text was updated successfully, but these errors were encountered: