f224fc5ea5
Subprocessed being interrupted resulted in it looking like those commands were executing successfully but with zero output. Interrupting the sudo prompt would result in any command running in sudo returning nothing and looking like it had succeeded. There was some clean up code in the lxc provider that nuked vagrant container state in the .vagrant directory if it looked like the container no longer existed based on the result of lxc-ls. Interrupting this check resulted in it looking like the container not existing, resulting in the provider code nuking the lxc dir in .vagrant. Voila
83 lines
2.8 KiB
YAML
83 lines
2.8 KiB
YAML
en:
|
|
vagrant_lxc:
|
|
messages:
|
|
not_created: |-
|
|
The container hasn't been created yet.
|
|
not_running: |-
|
|
The container is not currently running.
|
|
will_not_destroy: |-
|
|
The container '%{name}' will not be destroyed, since the confirmation
|
|
was declined.
|
|
starting: |-
|
|
Starting container...
|
|
force_shutdown: |-
|
|
Forcing shutdown of container...
|
|
warn_networks: |-
|
|
Warning! The LXC provider doesn't support public networks, the settings
|
|
will be silently ignored.
|
|
warn_group: |-
|
|
Warning! The LXC provider doesn't support the :group parameter for synced
|
|
folders. It will be silently ignored.
|
|
warn_owner: |-
|
|
Warning! The LXC provider doesn't support the :owner parameter for synced
|
|
folders. It will be silently ignored.
|
|
setup_private_network: |-
|
|
Setting up private networks...
|
|
remove_bridge: |-
|
|
Removing bridge '%{name}'...
|
|
|
|
vagrant:
|
|
commands:
|
|
status:
|
|
stopped: |-
|
|
The container is currently stopped. Run `vagrant up` to bring it up again.
|
|
|
|
actions:
|
|
lxc:
|
|
compressing_rootfs: Compressing container's rootfs...
|
|
|
|
share_folders:
|
|
preparing: Setting up mount entries for shared folders...
|
|
|
|
errors:
|
|
lxc_interrupt_error: |-
|
|
Interrupted
|
|
|
|
lxc_execute_error: |-
|
|
There was an error executing %{command}
|
|
|
|
For more information on the failure, enable detailed logging by setting
|
|
the environment variable VAGRANT_LOG to DEBUG.
|
|
|
|
lxc_incompatible_box: |-
|
|
The base box you are trying to use is not compatible with the installed
|
|
vagrant-lxc version. Supported box versions are %{supported} but %{found} was found.
|
|
|
|
lxc_template_file_missing: |-
|
|
The template file used for creating the container was not found for %{name}
|
|
box.
|
|
|
|
lxc_templates_dir_missing: |-
|
|
Unable to identify lxc templates path.
|
|
|
|
Looked up under: %{paths}
|
|
|
|
lxc_linux_required: |-
|
|
The LXC provider only works on Linux. Please try to use
|
|
another provider.
|
|
|
|
lxc_not_installed: |-
|
|
The `lxc` package does not seem to be installed or `lxc-create` is not accessible on the PATH.
|
|
|
|
lxc_redir_not_installed: |-
|
|
`redir` is not installed or is not accessible on the PATH.
|
|
|
|
lxc_container_already_exists: |-
|
|
There is container on your system with the same name you've specified
|
|
on your Vagrantfile (%{name}), please choose a different one or
|
|
run `lxc-destroy --name %{name}` and try again.
|
|
|
|
lxc_command_not_supported: |-
|
|
Command (lxc-%{command}) not supported in version %{version}.
|
|
This command is available with version %{available_version}.
|