Kshitiz Bakshi commented on MESOS-8593:

We're users of DC/OS Community edition, and hence our interface for Mesos is 
via Marathon. DC/OS Community Edition does not provide the support to use 
different image pull secrets for each task. 

In Docker containerizer case, everything already works by changing the creds 
file because Docker reads credentials on every image pull. We have our tooling 
to refresh the credentials. Migrating to UCR is blocked for us because of this 
issue, as mesos-agent does not read the passed file on each image pull.

> Support credential updates in Docker config without restarting the agent
> ------------------------------------------------------------------------
>                 Key: MESOS-8593
>                 URL: https://issues.apache.org/jira/browse/MESOS-8593
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization, docker
>            Reporter: Jan Schlicht
>            Priority: Major
> When using the Mesos containerizer with a private Docker repository with 
> {{--docker_config}} option, the repository might expire credentials after 
> some time, forcing the user to login again. In that case the Docker config in 
> use will change and the agent needs to be restarted to reflect the change. 
> Instead of restarting, the agent could reload the Docker config file every 
> time before fetching.

This message was sent by Atlassian JIRA

Reply via email to