In e.g.: you 'docker run -t -i' a 'bash' session and '.bashrc' is fucked up, container will forever respawn disallowing you to 'docker rmi' the used image .

docker rmi triangle/ubuntu-saucy-with-rvm 2>&1|grep ^Error|awk '{print $10}'|xargs docker rm

Oracle Software usually can not be downloaded during build without providing some credentials. If the binaries are downloaded using curl or wget the credentials will remain in the docker image. One solution would be to keep the binaries in the docker build context and use squash or multi stage builds. Alternatively it is also possible to use a local web server (docker container) to download the files locally.

• Start a simple web server to locally share the software during docker build.

docker run -dit \
  --hostname orarepo \
  --name orarepo \
  -p 80:80 \
 -v /data/docker/volumes/orarepo:/www \

Simple alias to execute base in docker container with some terminal settings

alias deo='function _deo() { if [ -n "${1}" ]; then docker exec -e COLUMNS="`tput cols`" -e LINES="`tput lines`" -it -u oracle ${1} bash --login; else echo "No docker container specified"; fi } ; _deo'
alias der='function _der() { if [ -n "${1}" ]; then docker exec -e COLUMNS="`tput cols`" -e LINES="`tput lines`" -it -u root ${1} bash --login; else echo "No docker container specified"; fi } ; _deo'