How to run InfluxDB as a foreground process on Docker using Mesos Marathon

OBJ: I want to start a daemon container with Marathon. I want influxdb to be the service running on the container.

  1. Using the Docker run command, I currently start the influxdb service in my daemon containers using supervisord. Is there a way of starting the influxDB service in the foreground directly?

  2. docker microservice apps restart over and over again in kubernetes
  3. Unable to push image to Docker Hub registry
  4. Parsing a string to an array output from command line
  5. docker run registry error 301 response missing Location header
  6. Docker Consul service ip advertised as internal docker ip
  7. Why the directory created after WORKDIR disappear
  8. Is there a way that Marathon can help to achieve this?

I really want to avoid using supervisord. I feel it is redundant as a process handler.

Thank you!

  • Docker instead of multiple VMs
  • 'sh: 1: file: not found' when creating a android emulator inside a docker container
  • Unable to connect to an ibmnode:latest-based container with putty over ssh
  • Docker swarm multiple managers and workers Vs
  • DRY Config for Docker build and App
  • Docker /bin/bash: nodemon: command not found
  • One Solution collect form web for “How to run InfluxDB as a foreground process on Docker using Mesos Marathon”

    You can run the Docker container natively with Marathon. Here’s an excellent guide for running Docker containers this way:

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