You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2020. It is now read-only.
In certain versions of Mesos prior to 1.2.1/1.3.0, a bug in Mesos (MESOS-6951) causes problems with app labels that contain new lines when Marathon also provides those app labels as environment variables. This issue would cause the marathon-acme container to fail to start.
An ugly workaround is to force Marathon to not store the app label as an environment variable by making the label longer than 512 bytes:
"HAPROXY_0_HTTP_FRONTEND_ACL_WITH_PATH": " acl path_{backend} path_beg {path}\n use_backend {backend} if path_{backend}\n ##################################################################\n # This is a terrible hack to make the value of the marathon app\n # label containing this config snippet longer than 512 bytes,\n # which is the threshold beyond which marathon doesn't try to turn\n # it into an environment variable.\n # See https://issues.apache.org/jira/browse/MESOS-6951 for an\n # explanation of why this is necessary.\n ##################################################################\n",
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
In certain versions of Mesos prior to 1.2.1/1.3.0, a bug in Mesos (MESOS-6951) causes problems with app labels that contain new lines when Marathon also provides those app labels as environment variables. This issue would cause the marathon-acme container to fail to start.
An ugly workaround is to force Marathon to not store the app label as an environment variable by making the label longer than 512 bytes:
The text was updated successfully, but these errors were encountered: