-
Notifications
You must be signed in to change notification settings - Fork 73
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
VM won't start without a TTY #141
Labels
Comments
Following up for anyone having the same issue; to allocate a pseudo-tty to this process, I installed tmux and used the following plist file. This works a treat (logging is removed in this one, add it back if you like): <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>EnvironmentVariables</key>
<dict>
<key>PATH</key>
<string>/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin</string>
</dict>
<key>Label</key>
<string>com.docker.machine.default</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/tmux</string>
<string>-c</string>
<string>/usr/local/bin/docker-machine start default; exit</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist> It would still be ideal to be able to launch xhyve without a tty though. |
@TomFrost thats not working for me..
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running macOS Sierra. Installed docker-machine (0.8.1) and docker-machine-driver-xhyve (0.2.3) from brew. Chown'ed to root and set the setuid bit.
docker-machine start default
in a terminal works great. The machine comes up wonderfully, volumes mount via NFS.However, starting the machine through a LaunchAgent fails. The only difference visible through
ps ax
is thatlaunchctl
obviously doesn't map a TTY to the process. Here's mycom.docker.machine.default.plist
for reproduction:Save that to
~/Library/LaunchAgents
and load withlaunchctl load ~/Library/LaunchAgents/com.docker.machine.default.plist
. Verify that xhyve is running with the correct parameters withps ax | grep xhyve
. The following gets dumped to/tmp/dm_out.log
:Execution hangs at that point.
/tmp/dm_err.log
has no data.That plist successfully launches the VM on other drivers, but I'm guessing this one requires an active TTY for some reason. Any ideas?
The text was updated successfully, but these errors were encountered: