You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Santhosh Kumar Shanmugham (JIRA)" <ji...@apache.org> on 2017/06/09 23:10:21 UTC

[jira] [Updated] (AURORA-1916) Incompatibility with mesos 1.2

     [ https://issues.apache.org/jira/browse/AURORA-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Santhosh Kumar Shanmugham updated AURORA-1916:
----------------------------------------------
    Fix Version/s: 0.18.0

> Incompatibility with mesos 1.2
> ------------------------------
>
>                 Key: AURORA-1916
>                 URL: https://issues.apache.org/jira/browse/AURORA-1916
>             Project: Aurora
>          Issue Type: Bug
>          Components: Executor
>    Affects Versions: 0.17.0
>         Environment: Ubuntu 16.04, Mesos 1.2
>            Reporter: Kostiantyn Bokhan
>             Fix For: 0.18.0
>
>
> The list of mesos-containerizer arguments has been changed since 1.2:
> {code}
> /usr/libexec/mesos/mesos-containerizer launch --help
> Usage: launch [options]
>   --[no-]help                      Prints this help message (default: false)
>   --launch_info=VALUE              
>   --namespace_mnt_target=VALUE     The target 'pid' of the process whose mount namespace we'd like
>                                    to enter before executing the command.
>   --pipe_read=VALUE                The read end of the control pipe. This is a file descriptor 
>                                    on Posix, or a handle on Windows. It's caller's responsibility 
>                                    to make sure the file descriptor or the handle is inherited 
>                                    properly in the subprocess. It's used to synchronize with the 
>                                    parent process. If not specified, no synchronization will happen.
>   --pipe_write=VALUE               The write end of the control pipe. This is a file descriptor 
>                                    on Posix, or a handle on Windows. It's caller's responsibility 
>                                    to make sure the file descriptor or the handle is inherited 
>                                    properly in the subprocess. It's used to synchronize with the 
>                                    parent process. If not specified, no synchronization will happen.
>   --runtime_directory=VALUE        The runtime directory for the container (used for checkpointing)
>   --[no-]unshare_namespace_mnt     Whether to launch the command in a new mount namespace. (default: false)
> {code}
> Mesos 1.1.0:
> {code}
> /usr/libexec/mesos/mesos-containerizer launch --help
> Usage: launch [options]
>   --capabilities=VALUE             Capabilities the command can use.
>   --command=VALUE                  The command to execute.
>   --environment=VALUE              The environment variables for the command.
>   --[no-]help                      Prints this help message (default: false)
>   --pipe_read=VALUE                The read end of the control pipe. This is a file descriptor 
>                                    on Posix, or a handle on Windows. It's caller's responsibility 
>                                    to make sure the file descriptor or the handle is inherited 
>                                    properly in the subprocess. It's used to synchronize with the 
>                                    parent process. If not specified, no synchronization will happen.
>   --pipe_write=VALUE               The write end of the control pipe. This is a file descriptor 
>                                    on Posix, or a handle on Windows. It's caller's responsibility 
>                                    to make sure the file descriptor or the handle is inherited 
>                                    properly in the subprocess. It's used to synchronize with the 
>                                    parent process. If not specified, no synchronization will happen.
>   --pre_exec_commands=VALUE        The additional preparation commands to execute before
>                                    executing the command.
>   --rootfs=VALUE                   Absolute path to the container root filesystem. The command will be 
>                                    interpreted relative to this path
>   --runtime_directory=VALUE        The runtime directory for the container (used for checkpointing)
>   --[no-]unshare_namespace_mnt     Whether to launch the command in a new mount namespace. (default: false)
>   --user=VALUE                     The user to change to.
>   --working_directory=VALUE        The working directory for the command. It has to be an absolute path 
>                                    w.r.t. the root filesystem used for the command.
> {code}
> It causes the next error:
> {code}
> Failed to parse the flags: Failed to load unknown flag 'command'
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)