simple-docker | A simple docker-compose setup for Perch or Runway | Continuous Deployment library

I may not know the answer to the issues you are running into but I think I may be able to share some pointers to help debug this.

First of all, if you are unable to view logs from the DC/OS UI, you can also go to /mesos and find the simple_docker task under Completed Tasks . It would show up as TASK_FAILED. Click on the Sandbox link on the right and then check stderr and stdout files for the task. There might be some clues there as to why it failed.

Another place to look can be to note the Agent IP from the Mesos UI where the task failed. SSH into the node and run sudo journalctl -u dcos-mesos-slave to see agent logs and try to find the logs corresponding to the failing task

One difference between the running the application as a Pod and a the App definition you shared is that your app definition is using DOCKER as the containerizer for the task while Pods use MESOS containerizer. I noticed that you are using a private docker registry for your docker images. One possibility is that if your private registry's certificate is not trusted by Mesos but docker is configured already to trust it:

See https://stackoverflow.com/a/24149795/99189 for why you can't ping your container. In general, don't expect to be able to do that. The only network access you have to the container is through the ports that you expose, 80 and 443 in this case.

From the perspective of running this in a docker container and using virtual hosts, you'll need your http client to send a Host: header when making requests to localhost:80/localhost:443.

Assuming you are testing with a browser, and that your vhost is user3174311.com, try the following:

• add the line 127.0.0.1 user3174311.com to your /etc/hosts
• visit user3174311.com in your browser

This is what should be happening:

• browser looks up user3174311.com in /etc/hosts and resolves it to 127.0.0.1
• browser sends an http request with a Host: user3174311.com header to 127.0.0.1:80
• docker is listening on this address and forwards the connection to port 80 in your container
• apache sees the request, looks at the Host: header and determines the correct virtual host to use

After that, it depends on your apache/symphony3 configuration. You'll have to post more details if it's not working.