compilebox
compilebox copied to clipboard
remove docker argument -d in DockerTimeout.sh
with -d ,docker can't bootup because of conflict of argument -d and argument --rm
Dose removing -d option work? I got error.
{ [Error: Command failed: time="2017-04-20T23:29:52+09:00" level=fatal msg="cannot enable tty mode on non tty input"
] killed: false, code: 1, signal: null } '' 'time="2017-04-20T23:29:52+09:00" level=fatal msg="cannot enable tty mode on non tty input" \n'
Instead, when I run with only -d option(deleting --rm), it works well.!
In my situation, removing -d option does well.
But that i remove —rm and run only with -d option also does work ok !
在 2017年4月20日,22:33,JeongTaekLim [email protected] 写道:
Dose removing -d option work? I got error.
{ [Error: Command failed: time="2017-04-20T23:29:52+09:00" level=fatal msg="cannot enable tty mode on non tty input" ] killed: false, code: 1, signal: null } '' 'time="2017-04-20T23:29:52+09:00" level=fatal msg="cannot enable tty mode on non tty input" \n' Instead, when I run with only -d option(deleting --rm), it works well.!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/remoteinterview/compilebox/pull/31#issuecomment-295759546, or mute the thread https://github.com/notifications/unsubscribe-auth/AFookb6VKj2DJYIva6FvnU32rWbeRtwhks5rx2yygaJpZM4M9rS1.
Thank you for reply. Can you tell me your os? Mine is Ubuntu 14.04 LTS
My docker runs on boot2docker , a toolbox for macOS. My macOS is 10.12.3.
i have seen your issues#32 , but i didn’t get into your problem on the first step.I run command ‘npm install’ and ‘node app.js’ well.
在 2017年4月21日,10:06,JeongTaekLim [email protected] 写道:
Thank you for reply. Can you tell me your os?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/remoteinterview/compilebox/pull/31#issuecomment-296015473, or mute the thread https://github.com/notifications/unsubscribe-auth/AFookUaK44CD_I3eHzbecSVNDB0hkEPdks5ryA8-gaJpZM4M9rS1.
This change is necessary.
Official Docs : https://docs.docker.com/engine/reference/run/#clean-up-rm
I've tried in a Digital Ocean droplet with CentOS and removing -d didn't work, while removing --rm did work.
As I understand this issue -d
and --rm
are not conflicting anymore. The official docs also say:
By design, containers started in detached mode exit when the root process used to run the container exits, unless you also specify the --rm option. If you use -d with --rm, the container is removed when it exits or when the daemon exits, whichever happens first.