Open madhosoi opened 3 years ago
The pipeline is using registry-image resource type. If I change it to docker-image, the pipeline works as expected.
Looking at the lchow man page: https://linux.die.net/man/2/lchown
It looks like the CAP_CHOWN
capability is required for it to run successfully. Looking at the code, we only attempt chowning if we're the root user https://github.com/concourse/registry-image-resource/blob/7e65e92c87d7dcc8a83508a0cf771526e38a2299/commands/unpack.go#L28
This is probably a problem specific to RKE or CentOS7. I'm not familiar with either systems. You could try adding the CAP_CHOWN
capability to the worker pods and see if that fixes the issue. I'm not convinced that'll fix the issue though. The registry-image pulling the image should be running under a non-root uid and therefore shouldn't go down that chown'ing codepath at all... Weird indeed.
@madhosoi Likely your persistentvolume does not support chown operations. If you're using NFS like me, ensure that no_root_squash
is enabled.
Hi all, I am testing to deploy concourse via helm, in an on-premise cluster deployed with RKE ( K8s version , based on CentOS7 nodes, with Kernel 5.4. Everything seems work fine, but when I start to run the first pipeline (helloworld) that tries to fetch a busybox image, I get this error:
Another useful information: Worker Persistent Volume via NFS3 I can setup Concourse in the same node type with Docker Compose and with Hashicorp Nomad and are running as expected.
Could you help me to understand why it happens?
Thanks!! Miguel