ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I am running into this issue as well with the ros:noetic-ros-core-focal as well as ros:noetic builds straight from dockerhub
docker run -it --rm ros:noetic-ros-core-focal bash
Fatal Python error: pyinit_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
2 | No.2 Revision |
I am running into this issue as well with the ros:noetic-ros-core-focal as well as ros:noetic builds straight from dockerhub
docker run -it --rm ros:noetic-ros-core-focal bash
Fatal Python error: pyinit_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
I think this issue is definitely tied to the arm32 architecture as I successfully performed the above test on arm64 and amd64 architectures.
3 | No.3 Revision |
I am running into this issue as well with the ros:noetic-ros-core-focal as well as ros:noetic builds straight from dockerhub
docker run -it --rm ros:noetic-ros-core-focal bash
Fatal Python error: pyinit_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
I think this issue is definitely tied to the arm32 architecture as I successfully performed the above test on arm64 and amd64 architectures.architectures. I also tried installing straight from ubuntu:focal following ros.org installation instructions, but there seems to be an issue with that too, as highlighted here : https://askubuntu.com/questions/1263284/apt-update-throws-signature-error-in-ubuntu-20-04-container-on-arm
4 | No.4 Revision |
I am running into this issue as well with the ros:noetic-ros-core-focal as well as ros:noetic builds straight from dockerhub
docker run -it --rm ros:noetic-ros-core-focal bash
Fatal Python error: pyinit_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
I think this issue is definitely tied to the arm32 architecture as I successfully performed the above test on arm64 and amd64 architectures. I also tried installing straight from ubuntu:focal following ros.org installation instructions, but there seems to be an issue with that too, as highlighted here : https://askubuntu.com/questions/1263284/apt-update-throws-signature-error-in-ubuntu-20-04-container-on-arm
After all this, what ended up working for me was running with the --security-opt seccomp:unconfined option. This appears to be tied to some issue with libseccomp package that is breaking debian builds for arm32.
docker run --rm --name noetic-dev -it --security-opt seccomp:unconfined ros:noetic bash
5 | No.5 Revision |
;tldr try --security-opt seccomp:unconfined
in your docker run command
I am running into this issue as well with the ros:noetic-ros-core-focal as well as ros:noetic builds straight from dockerhub
docker run -it --rm ros:noetic-ros-core-focal bash
Fatal Python error: pyinit_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
I think this issue is definitely tied to the arm32 architecture as I successfully performed the above test on arm64 and amd64 architectures. I also tried installing straight from ubuntu:focal following ros.org installation instructions, but there seems to be an issue with that too, as highlighted here : https://askubuntu.com/questions/1263284/apt-update-throws-signature-error-in-ubuntu-20-04-container-on-arm
After all this, what ended up working for me was running with the --security-opt seccomp:unconfined option. This appears to be tied to some issue with libseccomp package that is breaking debian builds for arm32.
docker run --rm --name noetic-dev -it --security-opt seccomp:unconfined ros:noetic bash