Corresponding Universe PR: mesosphere/universe#817

I am attempting to have kong listen on port 80 instead of 8000, and I updated the /usr/local/kong/nginx-kong.conf and Dockerfile to rebuilt the image:
server {
server_name kong;
listen 0.0.0.0:80;
……
}
Dockerfile:
FROM kong:0.10.3
COPY nginx-kong.conf /usr/local/kong/nginx-kong.conf
EXPOSE 80 8443 8001 7946

DC/OS network definition:

When following the example of gitlab-runner and trying to test it with DCOS 1.9, It gives an error.
Steps that can be taken to reproduce the issue:

1. Create an options.json with the following content:
   { "service": { "name": "gitlab-runner-shell" }, "gitlab": { "service-name": "gitlab.marathon.mesos", "registration-token": "Your_Registration-Token from GitLab" }, "gitlab-runner": { "executor": "shell", "tag-list": "build-as-docker,build-in-shell", "concurrent-builds": 4 } }
2. Run the following code from the terminal:
   dcos package install --options=options.json gitlab-runner
3. Following is the output:
   Package [gitlab-runner] not found
4. Also tried with the following options.json:
   { "service": { "name": "gitlab-runner-docker" }, "gitlab": { "service-name": "gitlab.marathon.mesos", "registration-token": "b_EsjLKVyXahggrFzZHr" }, "gitlab-runner": { "executor": "docker", "tag-list": "build-in-docker,docker", "concurrent-builds": 4, "docker-default-image": "node:6-wheezy", "docker-insecure-registry": "myregistry.mydomain.mytld" } }
5. It has the same result.

Corresponding Universe PR: mesosphere/universe#833

cc @m0ppers
Universe PR: mesosphere/universe#837

cc: @cgbaker @OhRobin

Colon in file names is forbidden and causes a lot of issues on Windows.
Files are not visible in file explorer, git is unable to work with them.

Files:
ceph/1.9/img/img:configure_secrets_in_exhibitor.png
ceph/1.8/img/img:configure_secrets_in_exhibitor.png

Universe PR: mesosphere/universe#842

Even if persistence is enabled during the installation, it won't take effect. The final service definition will end up with the following section:

...
  "env": {
        "STORAGE_PATH": "/var/lib/registry"
...

Which is wrong for two reasons:

1. The name of the environment variable changed to REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY when Docker developed a new version of the registry.
2. The value should point to the directory inside the local persistent volume directory which is inside the Mesos sandbox directory.

The section of the service definition above should look like:

...
  "env": {
        "REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY": "/mnt/mesos/sandbox/var/registry"
...

Thank you!
=Andrey

https://github.com/dcos/examples/tree/master/flink/1.9

I'm Running DC/OS on DigitalOcean and experiencing the same error as mentioned in Troubleshooting under "AWS Specific Config".

Could you please provide a solution for DigitalOcean?

This is what I'm getting on DigitalOcean, same as AWS:

2017-07-29 17:10:05,553 ERROR org.apache.flink.mesos.runtime.clusterframework.MesosApplicationMasterRunner  - Mesos JobManager initialization failed
java.net.UnknownHostException: agentname: agentname: Name or service not known
    at java.net.InetAddress.getLocalHost(InetAddress.java:1505)

mesos-elasticsearch isn't DC/OS elasticsearch

Current doc links to these which are unrelated:

• http://mesos-elasticsearch.readthedocs.io/en/latest/
• https://github.com/mesos/elasticsearch

Should probably link to:

• https://docs.mesosphere.com/service-docs/elastic/
• https://github.com/mesosphere/dcos-commons/tree/master/frameworks/elastic

Universe PR: mesosphere/universe#630

The example says "You should see a webpage similar to this: Welcome to DC/OS....".
In reality the default nginx page is shown. From looking at the code this looks correct, please either change package or update example.