![]() There is not checking on this command, so you can set it to whatever you want theoretically. This value gets overridden using the option. ![]() So for example, if the shell set for is not installed on the host system then Vagrant will return an error about the shell being invalid. For example, in this snippet, Vagrant prepares a command to run on the remote machine using the configured shell. The option allows users to set the shell to be used by Vagrant when connecting to the remote machine. It looks like the command sed -i '/#VAGRANT-BEGIN/,/#VAGRANT-END/d' /etc/fstab is not valid in the tclsh shell? You can disable this feature with the allow_fstab_modification config option.Ĭan anyone explain what exactly is vagrant doing with config-ssh-shell ? The issue you seem to be running into with vagrant 2.2.15 has to do with synced folders getting added to fstab. You're using the full path to the shell and that the shell isĬan anyone explain what exactly is vagrant doing with config-ssh-shell?Ĭan this setting be overridden? Could you point me to the source code and possible values?Ĭan vagrant be set to ignore such errors and continue executing the Vagrantfile? Using a shell that is unavailable on the system. The configured shell () is invalid and unable If I omit = "tclsh" then I get the following error => default: Booting VM. % Unrecognized command found at '^' position. Sed -i '/#VAGRANT-BEGIN/,/#VAGRANT-END/d' /etc/fstab Vagrant assumes that this means the command failed! The following SSH command responded with a non-zero exit status. ![]() When I use vagrant 2.2.15 from Hashicorp repo it fails with error below. In order for the vm to not error out when vagrant tries to connect to it, I use one of the available shells, which are not fully featured, as a workaround. I packed a network appliance with vagrant 2.2.6 from apt repo on ubuntu 20 / wsl 1 / windows 10.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |