You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Michael Park (JIRA)" <ji...@apache.org> on 2015/10/20 02:16:27 UTC
[jira] [Commented] (MESOS-3692) Clarify error message 'could not
chown work directory'
[ https://issues.apache.org/jira/browse/MESOS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964288#comment-14964288 ]
Michael Park commented on MESOS-3692:
-------------------------------------
{noformat}
commit 4f845eac6390f77d8191b275261ee89b70b6d10c
Author: Marco Massenzio <ma...@mesosphere.io>
Date: Mon Oct 19 17:02:06 2015 -0700
Enhanced documentation of the `--switch_user` flag on the agent.
Review: https://reviews.apache.org/r/39447
{noformat}
> Clarify error message 'could not chown work directory'
> ------------------------------------------------------
>
> Key: MESOS-3692
> URL: https://issues.apache.org/jira/browse/MESOS-3692
> Project: Mesos
> Issue Type: Documentation
> Components: documentation
> Affects Versions: 0.25.0
> Reporter: Frank Scholten
> Assignee: Marco Massenzio
> Priority: Minor
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> When deploying a framework I encountered the error message 'could not chown work directory'.
> It took me a while to figure out that this happened because my framework was registered as a user on my host machine which did not exist on the Docker container and the agent was running as root.
> I suggest to clarify this message by pointing out to either set {{--switch-user}} to {{false}} or to run the framework as the same user as the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)