concourse: runs can't create container because of strange owner.

concourse 3.6 binary deployment baremetal installation (centos 7.3)

I try hello.yml ` $ cat hello.yml [20:33:54] jobs:

  • name: hello-world plan:
    • task: say-hello config: platform: linux image_resource: type: docker-image source: {repository: ubuntu} run: path: echo args: [“Hello, world!”]`

as result:

runc create: exit status 1: container_linux.go:264: starting container process caused “process_linux.go:339: container init caused "rootfs_linux.go:56: mounting \"/opt/concourse/work/3.6.0/assets/bin/init\" to rootfs \"/opt/concourse/work/volumes/live/6634507c-eeb9-446c-555b-d79d46b016ed/volume/rootfs\" at \"/opt/concourse/work/volumes/live/6634507c-eeb9-446c-555b-d79d46b016ed/volume/rootfs/tmp/garden-init\" caused \"open /opt/concourse/work/volumes/live/6634507c-eeb9-446c-555b-d79d46b016ed/volume/rootfs/tmp/garden-init: permission denied\""”

also i see next picture: [root@ci live]# ls 630a1549-5080-4e82-7d80-65a1e391b534/ privileged.json properties.json ttl.json volume [root@ci live]# ls -lh /opt/concourse/work/volumes/live/630a1549-5080-4e82-7d80-65a1e391b534/ total 16K -rw-r–r-- 1 root root 6 Oct 27 16:23 privileged.json -rw-r–r-- 1 root root 5 Oct 27 16:23 properties.json -rw-r–r-- 1 root root 34 Oct 27 16:23 ttl.json drwxr-xr-x 3 4294967294 4294967294 4.0K Oct 27 16:23 volume

how to resolve this problem?

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 18 (14 by maintainers)

Commits related to this issue

Most upvoted comments

I have the same problem trying to set up a live environment for the first time, with all testing environments having worked flawlessly. Setup with either docker-compose according to docs or the standalone binary. Using hello.yml from the docs, which includes an image_resource. Fixing the owner of the folders works temporarily but this is essentially gone the next time the container runs.

Please do not spam.