This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
Avoid Timed out error when umask is 027 or 077
#435
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If LXC commands are run with a restrictive umask like 027 or 077, then
the root directory of new containers will lack read `r` and access `x`
permission for non-root users. The first failure to result from this
during `vagrant up` is that the SSH daemon cannot read the crucial file
`/home/vagrant/.ssh/authorized_keys` after it drops privileges to the
level of the `vagrant` user. The result is the familiar:
```
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
```
So we should make sure that we run all LXC commands with a umask that at
least does not prevent group and world `r` and `x` bits from being set
in newly created files and directories.
|
Nice. I just saw this, and unfortunately also came up with my own fix. I took a different approach as seen here: sitepoint@61b384a |
ghost
self-assigned this
|
Interesting problem. I could reproduce it as well. It might be a problem with LXC directly if I look at lxc/lxc#1403 . @boltronics I like the elegance of your solution, but @brandon-rhodes' solution has the advantage of working even when the user hasn't installed the sudo wrapper. Testing the fix, then merging. |
|
Does the trick. Thanks @brandon-rhodes |
ghost
merged commit
This pull request was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If LXC commands are run with a restrictive umask like 027 or 077, then
the root directory of new containers will lack read
rand accessxpermission for non-root users. The first failure to result from this
during
vagrant upis that the SSH daemon cannot read the crucial file/home/vagrant/.ssh/authorized_keysafter it drops privileges to thelevel of the
vagrantuser. The result is the familiar:So we should make sure that we run all LXC commands with a umask that at
least does not prevent group and world
randxbits from being setin newly created files and directories.