This sections contains tips how to setup Marathon. E.g. you might need to tweak the configuration of Marathon to run well in certain cloud environments. You are invited to contribute your tips to our documentation!
A reference for all configuration options which are specified as command line options is available here.
By default, CoreOS does not populate /etc/hosts which may lead to Marathon crashing on startup.
You may see something like this in Marathon logs (or syslog)
F0728 00:56:32.080438 1571 process.cpp:889] Name or service not known
The easy way to fix is to allow CoreOS to manage /etc/hosts with the manage_etc_hosts: localhost attribute in your cloud config. Refer to the CoreOS Cloud-Config documentation for more details.
Check lookups work by running hostname -f and verify it returns successfully (exit code 0)
Similar to CoreOS, sometimes Azure Linux VMs (observed mostly on Ubuntu) are missing a hostname entry in /etc/hosts. If you find running sudo commands takes a long time or hostname -f exits with an error, modify your /etc/hosts file and prepend it with an entry for your current hostname. E.g. ‘127.0.0.1 {my-host-name}’
Once hostname -f returns successfully, Marathon should be able to start.
The default executor timeout on Mesos agents or Marathon’s task_launch_timeout are too low for Docker containerizers (docker pull can take some time…). Refer to the docs on Docker Containers