start redis-server on debian/ubuntu boot

I am trying to create a docker container where redis starts at boot.
there will be other foreground services running on that other container which will connect to the redis db.

for some reason the service does not start when i run the container.
here my simplified Dockerfile

  • Increasing Docker container size on Centos
  • Docker container CPU and Memory Utilization
  • Unable to access the webapplication through container IP in service fabric cluster VM
  • Timeout pushing image to nexus inside container docker
  • How to use properly centos dockerfile with ubuntu host?
  • seafile docker - how to persist config/make container disposable
  • FROM debian
    # this solves an issue described here:
    RUN sed -i -e s/101/0/g /usr/sbin/policy-rc.d
    # install redis-server
    RUN apt-get update && apt-get install -y redis-server
    # updates init script (redundant)
    RUN update-rc.d redis-server defaults 
    # ping google to keep the container running in foreground
    CMD ["ping", ""]

    can anybody explain me why this is not working and how this should be done right?

  • Cannot seem to install Google Cloud Managed VMs
  • Docker run multiple commands, tee to logfile, and missing SIGTERM
  • docker exec command not executing in sh file
  • Docker. Make volume on postgresql container
  • docker swarm 1.1.3: No such image after pulling from public repo, and trying to tag
  • Internet access lost on host after docker installation on linux Mint 17
  • One Solution collect form web for “start redis-server on debian/ubuntu boot”

    So a docker container is like a full OS but has some key differences. It’s not going to run a full init system. It’s designed and intended to run a single process tree. While you can run a supervisor such as runit et al within a container, you are really working against the grain of docker and all the tooling and documentation is going to lead you away from using containers like VMs and toward the harmony of 1 process/service per container.

    So redis isn’t starting because the ping command is literally the only process running in your container.

    there will be other foreground services running on that other container which will connect to the redis db.

    Don’t do it this way. Really. Everything will be easier when you put 1 process in each container and connect them via network links.

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