Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unwanted ports bound when running a docker image #8709
I've created a new repository by committing an existing (but not running) container to a new name (e.g. mysoft).
The problem is that when I run it as:
docker run -t -i mysoft /bin/bash
The ports that I used to bind to the older container / image by using the '-p' parameter are exposed in this new container.
Is this the expected behavior?. How can I get rid of it and run my new repo/image without exposing any of these older ports?.
UNEXPOSE would be nice to have. When I "inherit" from another container and change the port, the old one (here 9000/tcp) still shows up
1c4c9c9fdf08 mulle/mediawiki:wheezy "/usr/sbin/php5-fpm 17 hours ago Up 17 hours **9000/tcp**, 172.17.42.1:9001->9001/tcp mediawiki