chroot: cannot change root directory to '/': Operation not permitted about carla-autoware

[mrm-mmh]

I've been able to find a workaround by adding sudo rights to the user in the run.sh and launching with sudo:

#!/bin/bash

XSOCK=/tmp/.X11-unix
XAUTH=$HOME/.Xauthority

VOLUMES="--volume=$XSOCK:$XSOCK:rw
         --volume=$XAUTH:$XAUTH:rw
         --volume=$(pwd)/autoware-contents:/home/autoware/autoware-contents:ro"

RUNTIME=""
DOCKER_VERSION=$(docker version --format '{{.Client.Version}}' | cut --delimiter=. --fields=1,2)
if [[ $DOCKER_VERSION < "19.03" ]] && ! type nvidia-docker; then
    RUNTIME="--gpus all"
else
    RUNTIME="--runtime=nvidia"
fi

docker run \
    -it --rm \
    $VOLUMES \
    --env="XAUTHORITY=${XAUTH}" \
    --env="DISPLAY=${DISPLAY}" \
    --privileged \
    --net=host \
    --user $(id -u ${USER}):$(id -g ${USER}) \
    --group-add sudo \
    $RUNTIME \
    carla-autoware:latest

sudo ./run.sh

However, I agree with wuxiaohua1011 that the container should be adapted so that sudo is not required.

Hope that helps for now!

[wuxiaohua1011]

I've been able to find a workaround by adding sudo rights to the user in the run.sh and launching with sudo:

#!/bin/bash

XSOCK=/tmp/.X11-unix
XAUTH=$HOME/.Xauthority

VOLUMES="--volume=$XSOCK:$XSOCK:rw
         --volume=$XAUTH:$XAUTH:rw
         --volume=$(pwd)/autoware-contents:/home/autoware/autoware-contents:ro"

RUNTIME=""
DOCKER_VERSION=$(docker version --format '{{.Client.Version}}' | cut --delimiter=. --fields=1,2)
if [[ $DOCKER_VERSION < "19.03" ]] && ! type nvidia-docker; then
    RUNTIME="--gpus all"
else
    RUNTIME="--runtime=nvidia"
fi

docker run \
    -it --rm \
    $VOLUMES \
    --env="XAUTHORITY=${XAUTH}" \
    --env="DISPLAY=${DISPLAY}" \
    --privileged \
    --net=host \
    --user $(id -u ${USER}):$(id -g ${USER}) \
    --group-add sudo \
    $RUNTIME \
    carla-autoware:latest

sudo ./run.sh

However, I agree with wuxiaohua1011 that the container should be adapted so that sudo is not required.

Hope that helps for now!

Nice, it works great, thank you so much!

[wuxiaohua1011]

Actually, I looked into this issue a bit, and it seems like this stack overflow says that you actually cannot start a docker at the root directory or something like that
https://stackoverflow.com/questions/40636618/how-to-start-a-chrooted-directory-as-a-docker-container

Which means that the docker file might have a small problem?

[charles-lei]

I have the same problem.

[twada-cats]

I also have same problem when run.sh is executed. I changed user as root before execution.
$ sudo su
$ ./run.sh
It did not works. Can you tell us how to solve it?

[joel-mb]

Hi! The issue should be fixed now (#103). Feel free to re-open the issue if needed.