You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started getting this error a couple weeks ago. Things were working previously, no changes on my end. Seems like a permissions issue, maybe something moved in the Humble container?
+ .industrial_ci/bitbucket.sh ROS_DISTRO=humble
Running test 'source_tests'
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
pull_docker_image
$ docker pull ros:humble
humble: Pulling from library/ros
Digest: sha256:482ae18aa5d4813dd5c59aee9e4cd830eac94c60587f494e9ff343e6aaf3aba3
Status: Image is up to date for ros:humble
[docker.io/library/ros:humble](http://docker.io/library/ros:humble)
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
'pull_docker_image' returned with code '0' after 0 min 0 sec
$ docker create --init --env-file /opt/atlassian/pipelines/agent/build/.industrial_ci/industrial_ci/src/isolation/docker.env --rm -v /opt/atlassian/pipelines/agent/build:/opt/atlassian/pipelines/agent/build:ro -e TARGET_REPO_PATH=/opt/atlassian/pipelines/agent/build -v /opt/atlassian/pipelines/agent/build/.industrial_ci/industrial_ci/src:/opt/atlassian/pipelines/agent/build/.industrial_ci/industrial_ci/src:ro -e ICI_SRC_PATH=/opt/atlassian/pipelines/agent/build/.industrial_ci/industrial_ci/src -t --entrypoint -w /opt/atlassian/pipelines/agent/build ros:humble /bin/bash /opt/atlassian/pipelines/agent/build/.industrial_ci/industrial_ci/src/run.sh source_tests run_source_tests
Copy credentials: /root/.ssh
$ docker start -a 20009b05269ff92d6267794c18b3c20192fb9cf79a48493ab9f4ad23938c6815
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/usr/local/bin/docker-init" to rootfs at "/sbin/docker-init": mount /proc/self/fd/7:/sbin/docker-init (via /proc/self/fd/13), flags: 0x1021: operation not permitted: unknown
Copy credentials: /root/.ssh
$ docker start -a 20009b05269ff92d6267794c18b3c20192fb9cf79a48493ab9f4ad23938c6815
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/usr/local/bin/docker-init" to rootfs at "/sbin/docker-init": mount /proc/self/fd/7:/sbin/docker-init (via /proc/self/fd/13), flags: 0x1021: operation not permitted: unknown
In an attempt to debug I added an ls command to bitbucket-pipelines.yaml prior to the industrial_ci script:
- ls /usr/local/bin
- .industrial_ci/bitbucket.sh ROS_DISTRO=humble
It shows that /usr/local/bin is empty
The text was updated successfully, but these errors were encountered:
Found some info here. Apparently this is due to a bitbucket upgrade.
The docker run --init command is currently not supported. If you attempt to use this parameter with docker run or specify init: true in Docker Compose, you will encounter an error message similar to the following:
I started getting this error a couple weeks ago. Things were working previously, no changes on my end. Seems like a permissions issue, maybe something moved in the Humble container?
In an attempt to debug I added an
ls
command to bitbucket-pipelines.yaml prior to the industrial_ci script:It shows that
/usr/local/bin
is emptyThe text was updated successfully, but these errors were encountered: