root@iZ25pamnfsuZ:/var/discourse# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
local_discourse/app latest 6d767d577160 27 seconds ago 1.812 GB
samsaffron/discourse 1.0.12 2285ff53ab18 12 weeks ago 1.217 GB
busybox latest 8c2e06607696 4 months ago 2.433 MB
The error was reported at the time of startup../launcher start app
1b3dd113bfcce18cc29ce63265fcd1ab930400d838396ffea98e1723220c3133
Error response from daemon: Cannot start container 1b3dd113bfcce18cc29ce63265fcd1ab930400d838396ffea98e1723220c3133: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
Port 80 cannotkill
Oh, there are other web services running online
root@iZ25pamnfsuZ:/var/discourse# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
local_discourse/app latest 6d767d577160 3 hours ago 1.812 GB
samsaffron/discourse 1.0.12 2285ff53ab18 12 weeks ago 1.217 GB
busybox latest 8c2e06607696 4 months ago 2.433 MB
docker run -d -p 8080:80 tutum/lamp
After modifying port 80, it is as follows
root@iZ25pamnfsuZ:/var/discourse# docker run -d -p 8080:80 local_discourse/app
f42e59fbb40384e971ade4ead24d93929f7df1fb8bcb74fb6d78ce3a17a52d65
root@iZ25pamnfsuZ:/var/discourse# ./launcher start app
starting up existing container
+ /usr/bin/docker start app
Error response from daemon: Cannot start container app: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
Error: failed to start containers: [app]
After implementation, it is still wrong.
Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
Can’t you see? You check what occupied port 80, and then
kill
Drop it.