You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm struggling why, but the only workaround i get know to spawn systemd containers (vivid) on trusty hosts is to set use_vt=True as lxc-start seems to mis behave with fds and classical cmd.run.
Thus for now, the safety belt is to activate vt for lxc-start.
See for implementation: #23982
Without using use_vt, the lxc-start command will (not reproducible everywhere :(, and i didnt found the origin now) hang forever.
The text was updated successfully, but these errors were encountered:
kiorky
changed the title
systemd lxc containers need use_vt=True at start
systemd lxc containers need use_vt=True at lxc-start stage
May 31, 2015
I had reproduced this bug only on 2 hosts (on 50 others, everything was fine).
But i reproduce it constantly on them without any obvious reason, and the configuration is the same everywhere.
I'm struggling why, but the only workaround i get know to spawn systemd containers (vivid) on trusty hosts is to set use_vt=True as lxc-start seems to mis behave with fds and classical cmd.run.
Thus for now, the safety belt is to activate vt for lxc-start.
See for implementation: #23982
Without using use_vt, the lxc-start command will (not reproducible everywhere :(, and i didnt found the origin now) hang forever.
The text was updated successfully, but these errors were encountered: