Start tor and polipo when I launch my container

I wrote my first Dockerfile in order to test Docker with tor and polipo.
My Dockerfile looks like:

# Pull base image.
FROM ubuntu:latest

# Upgrade system
RUN apt-get update && apt-get dist-upgrade -y --no-install-recommends && apt-get autoremove -y && apt-get clean

# Install TOR
RUN apt-get install -y --no-install-recommends tor tor-geoipdb torsocks && apt-get autoremove -y && apt-get clean

RUN apt-get update && apt-get install -y polipo

# Default ORPort

# Default DirPort 

# Default SOCKS5 proxy port 

# Default ControlPort
# Default polipo Port

RUN echo 'socksParentProxy = "localhost:9050"'  >> /etc/polipo/config
RUN echo 'socksProxyType = socks5'  >> /etc/polipo/config
RUN echo 'diskCacheRoot = ""' >> /etc/polipo/config

RUN echo 'ORPort 9001' >> /etc/tor/torrc
RUN echo 'ExitPolicy reject *:*' >> /etc/tor/torrc

RUN mkdir scrapy
ADD scrapyTor scrapy

RUN chmod 775 ./

my contains 3 lines:

  • docker-compose: specify which interface will connect to each network (when having multiple networks)
  • Docker Compose circular container linking
  • Docker toolbox cannot allocate memory
  • Trouble using AUFS driver in docker with Ubuntu
  • Docker restore volume of removed container?
  • Docker-compose extend not finding environment variables
  • #!/bin/bash                                                              
    /etc/init.d/tor start &
    /etct/init.d/polipo start &

    But when I launch this command:

    docker run -i -t id_image /bin/bash

    And once inside in the container when I launch ps, I see nothing.
    How I can resolve this?

  • aws container service \ how dockers configured for communicating with each other
  • How come that `docker-compose up` throws an error where `docker run` works fluently
  • docker login - error storing credentials - write permissions error
  • docker hub webhook for _failed_ build?
  • Docker + Kitematic NAT container
  • Building WAR
  • One Solution collect form web for “Start tor and polipo when I launch my container”

    Your Dockerfile should have a command defined like:

    CMD ./

    Then you do not need to provide /bin/bash as a run command. Only the following should be enough:

    docker run -i -t id_image

    By the way: your script file creates two processes running in background. That will not work!

    Docker containers need to have always a process in foreground. In your case the container would stop immediately after executing your start script. And while stopping the SIGTERM will not properly be sent to those background processes so they will simply get killed and may leave some corrupt data.

    You should think about using supervisord instead when you need to have multiple processes in your container started.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.