I'm running a ZABBIX server (including Web/DB) on a virtual server or container using vagrant or Docker.
The Web console cannot be accessed because of private IP address conflicts.
I would like to know how to troubleshoot in such cases.
Below is what you did yourself.
- Execute ifconifig on the host OS and confirm the network segment to which you belong (assuming 192.168.2.0/24)
- Try to ping an IP address that will not exist in the same network segment (192.168.2.150 or nobody will use it!)
- As a result of ping, there seemed to be no problem, so edit the vagranfile and start a new virtual server
I'm not familiar with the network, so I'd be happy if someone could tell me.
If information is missing, add it.
Answer # 1
Is there a conflict with private IP addresses?
How did you check this?
I think that it will not compete because the network can usually be done in Docker ...
It may be easy to answer if you let us know Docker's host OS.
Docker for Macand
Linux Dockerhave different network configurations.
Answer # 2
When starting a new virtual machine, instead of your own machine,
Is there any reason why you are going to get a new IP address for the router?
For example, Vagrant relies on VirtualBOX (which can be anything else if you have a plug-in) to create a virtual machine, but
When VirtualBOX is installed, a virtual LAN should be built in your machine so that the host machine can act as a parent ≒ router.
I think that it will come out if you examine it by how to write Vagrantfile, so please investigate.
Although this question is probably a work environment,
If the IP addresses are scattered enough to cause a collision within the LAN, there may be a network administrator who manages the IP addresses.
If that is the case, it would be against the rules for you to occupy the IP address yourself.
If you have an IP address manager at your workplace, please consult with them.
Since "starting ZABBIX server (including Web/DB)" is a valid reason, it should be approved in two replies.
- after executing vagrant up, it stops with a private key and times out
- centos - setting the private address of the db server
- Analysis of the method of obtaining the IP address by resolving the domain name in Python
- assigning ip address when launching the second server in one environment with vagrant does not work
- ccna - about ipv4 private ip address range
- windows 7 - vagrant up stops at "ssh auth method: private key"
- virtualbox - in vagrant, ssh auth method: stops with private key
- is the ip address specified by udp a global ip? private ip?
- macos (osx) - command to get only private ip address on mac
- vagrant - i can't see the screen with the ip address of the guest os
- windows - when vagrant, default: ssh auth method: private key stops
- virtualbox - about vagrant ip address settings
- tcp - how to name a machine with only a private ip address from outside the lan
- virtualbox - cannot add vagrantbox (mac?)
- linux - what's easier with docker and vagrant? (for server side engineers)
- unix - i did rm -r
- i want to import sql file into docker container (mysql) created on vagrant + virtualbox
- i want to run minikube on vagrant linux
- even with docker for mac virtualbox → vagrant → docker i am having trouble connecting to localhost
- macos (osx) - i want to make wordpress with vagrant/docker, but "this page is not working" is returned