Brandon Rhodes 43aa9bfb3e Avoid Timed out error when umask is 027 or 077 ... 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.		2017-01-29 13:53:09 -05:00
..
vagrant-lxc	Avoid Timed out error when umask is 027 or 077	2017-01-29 13:53:09 -05:00
vagrant-lxc.rb	Remove version suffix from generated sudoers commands	2014-09-22 23:07:12 -03:00