Vagrant Port Collision на порту 80, но порт 80 не пересылается в VagrantFile - PullRequest
0 голосов
/ 24 января 2019

Я следую простому учебнику, который указывает мне установить Tomcat с Vagrant:

vagrant init emessiha/ubuntu64-java --box-version 1.0.0

Затем он советует мне отредактировать VagrantFile для пересылки с 8080 до 8080, а затем выполнить "vagrant up".При запуске "vagrant up" я получаю это сообщение:


Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 80 is already in use
on the host machine.

To fix this, modify your current project's Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

   config.vm.network :forwarded_port, guest: 80, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding. You could
try 'vagrant reload' (equivalent of running a halt followed by an up)
so vagrant can attempt to auto-correct this upon booting. Be warned
that any unsaved work might be lost.

Вот мой VagrantFile.Вы можете видеть, что порт 80 не пересылается.

Я попытался изменить порты переадресации в VagrantFile с 8080 на 8081, и это не помогло устранить проблему.Затем я прокомментировал строку.Все та же проблема.Я на Mac с Высокой Сьеррой.


# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.box = "emessiha/ubuntu64-java"
  config.vm.box_version = "1.0.0"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  config.vm.network "forwarded_port", guest: 8080, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end

1 Ответ

0 голосов
/ 25 января 2019

Порты жестко запрограммированы в файле vagrant

Если вы посмотрите документацию для этого бродячего файла , это показывает, что следующие порты уже определены

  • 3306
  • 80
  • 8080

Я попытался раскрутить тот же бродячий ящик и обнаружил, что он использует те же порты

vagrant init emessiha/ubuntu64-java \
  --box-version 1.0.0
vagrant up
==> default: Forwarding ports...
    default: 80 (guest) => 80 (host) (adapter 1)
    default: 80 (guest) => 8080 (host) (adapter 1)
    default: 3306 (guest) => 3306 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...

Если вы попытаетесь переопределить, какие порты будет использовать блок, он добавляет эти порты вместо их замены.

Здесь я попытался переслать 3306 на 3307. Вместо того, чтобы заменить порт вперед, он добавил новую запись.

  config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
  config.vm.network "forwarded_port", guest: 3306, host: 3307, host_ip: "127.0.0.1"
    default: 80 (guest) => 80 (host) (adapter 1)
    default: 80 (guest) => 8080 (host) (adapter 1)
    default: 3306 (guest) => 3306 (host) (adapter 1)
    default: 3306 (guest) => 3307 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)

Поскольку этот бродячий ящик обслуживается кем-то другим, вы зависите от определений портов, которые они определили. Либо выясните, какая программа уже использует порт 80, и остановите его. (netstat -plnt в Linux) или создайте свой собственный бродячий ящик.

...