Are there any small partners deploying SNMP environment in docker?
At present, I have deployed SNMP environment in docker based on Ubuntu, but testing with mib brower locally always reports errors.
Attached is my deployed docker image.
docker pull registry.cn-hangzhou.aliyuncs.com/lovekun/ubuntu-16.04:2.0.1
The image is only compiled with snmp, and snmpd has not been configured. there is no problem in executing snmpget, snmpwalk and other commands in the doc, but the SNMP information requested in the doc is in this machine.
My approach is as follows:
Firstly, the container is operated based on the above:
run -it -p 161:161/udp registry.cn-hangzhou.aliyuncs.com/lovekun/ubuntu-16.04:2.0.1 /bin/bash
Follow the instructions given in the official documentation for configuring snmpd (http://www.net-snmp.org/wiki/ …Configure snmpd.
Start snmpd:/usr/local/sbin/snmpd start
However, after startup, there is no information output.
Check that there is no problem with the port:
On this machine, check the port and find that port 161 is not in listening state.
I would like to know if there have been any small partners involved. Under the guidance, which step has gone wrong?
Thank you for inviting me. I didn’t know about using snmp in detail, but your visual observation is that the principle of docker is not clear. The binding port problem is because the version of docker running 1.x on windows requires vbox to run on a linux kernel virtual machine. The new version of docker also has 2 modes of operation. If the DockerToolBox is used, docker-machine will create a virtual machine that you can use.
docker-machine ip defaultLooking at the network, I think your mistake is because host, that is, your win host and docker host, are not inside the unified network.
The above is to check your docker network and windows host network.
If you visit, you can add ip:port.
It is believed that most users using docker under windows are installed by dockerTool, so you can only regard the Docker running environment as a new vm host.