Can docker not be accessed externally without setting port mapping?

is working on open-falcon of Xiaomi, one of which is retrieved from docker .
follow the tutorial and execute docker"s:

-sharp make the imagerun commands under dir of dashboard:
docker build -t falcon-dashboard:v1.0 .

-sharp start the container
docker run -itd --name aaa --net host \
    -e API_ADDR=http://127.0.0.1:8080/api/v1 \
    -e PORTAL_DB_HOST=127.0.0.1 \
    -e PORTAL_DB_PORT=3306 \
    -e PORTAL_DB_USER=root \
    -e PORTAL_DB_PASS=123456 \
    -e PORTAL_DB_NAME=falcon_portal \
    -e ALARM_DB_PASS=123456 \
    -e ALARM_DB_HOST=127.0.0.1 \
    -e ALARM_DB_PORT=3306 \
    -e ALARM_DB_USER=root \
    -e ALARM_DB_PASS=123456 \
    -e ALARM_DB_NAME=alarms \
    falcon-dashboard:v1.0

from the above command, you don"t see anything that-p is used to bind port mappings, but somehow you can still request the port of an item in the docker container.
that"s weird.

Apr.01,2021

you still haven't noticed the command

< hr >

host Mode
host it can share Root Network Namespace with the host. The container has full permission to manipulate the host's network configuration. For security reasons, this mode is not recommended.
starting host mode is very simple. You can still add -- net=host parameter to docker run .

in addition, there are none mode, container mode, bridge mode (default mode), overlay mode


-- the net option has been set for docker's network. See

Previous: Mobile page scrolling problem

Next: Upload content using quill.js, preview content smaller on mobile

Menu