Package: vagrant Version: 2.2.9+dfsg-1 Severity: normal Hello
Vagrant running with provider as docker and with default settings will not start due to its naming, unless .name field is explicitly given in Vagrantfile. This is not the case for other providers. Below is the stderr Command: ["docker", "run", "--name", "_default_1594301896", "-d", "-v", "/:/vagrant", "docker.io/roboxes/centos6:latest", {:notify=>[:stdout, :stderr]}] /usr/bin/docker: Error response from daemon: Invalid container name (_default_1594301896), only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed. See '/usr/bin/docker run --help' This is solved by having something similar in my Vagrantfile config.vm.provider "docker" do |d| d.name = "foo-bar" -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vagrant depends on: ii curl 7.68.0-1 ii libarchive-tools 3.4.0-2 ii openssh-client 1:8.2p1-4 ii rsync 3.1.3-8 ii ruby 1:2.7+1 ii ruby-bcrypt-pbkdf 1.0.1-1+b2 ii ruby-childprocess 3.0.0-1 ii ruby-ed25519 1.2.4-1+b3 ii ruby-erubis 2.7.0-3 ii ruby-i18n 1.8.3-1 ii ruby-listen 3.1.5-2 ii ruby-log4r 1.1.10-4 ii ruby-net-scp 3.0.0-1 ii ruby-net-sftp 1:2.1.2-4 ii ruby-net-ssh 1:6.1.0-1 ii ruby-rest-client 2.0.2-3.1 ii ruby-vagrant-cloud 2.0.3-1 ii ruby-zip 2.0.0-2 Versions of packages vagrant recommends: ii vagrant-libvirt 0.0.45-2 Versions of packages vagrant suggests: pn virtualbox <none> -- no debconf information