4

I use Docker image from github to have a Ubuntu with xrdp, but when I make some changes (for example create new folder), exit the container, commit changes and create new image, I can't start container from this new image. I'm getting this kind of message:

 * Starting enhanced syslogd rsyslogd
   ...done.
 * Removing stale PID file /var/run/dbus/pid.
 * Starting system message bus dbus

 Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": Address already in use

I start docker container with:

docker run b3bdcd8a8a9d -p 3391:3389 2f60daa82fce

then connect with RDP, make some changes, disconect, stopping container and commiting changes with

docker commit 7d372287aa09 test

I use Ubuntu 14.04.2.

What could be the cause of such behavior?

skywalker
  • 318
  • 4
  • 10
  • That error message suggests that there is another program using the port `3391`. Are you using `docker stop` to stop the container? – Samuel Toh Jul 05 '17 at 00:25
  • it would help you to view what ports are busy ... what is your host OS ? the one where you launch your docker commands ? if its linux then issue this to display what processes are using what ports ... sudo netstat -peanut – Scott Stensland Jul 05 '17 at 01:03
  • stop the containers and start again – Anar Bayramov Jul 05 '17 at 03:09
  • The port `3391` is not used, there is no problem with running new container from the orginal image. I used `docker stop` and also try `docker pause`. Host OS is Ubuntu 14.04.02. – skywalker Jul 05 '17 at 07:46
  • I have the same problem – ahoffer May 10 '20 at 21:45

0 Answers0