Closed cjohansen closed 6 years ago
I'm really not sure if this belongs here, with Concourse itself, or if I did something wrong, so sorry in advance.
We have concourse running on AWS with concourse-up, but pipelines are failing with this:
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 \\\"/var/vcap/data/baggageclaim/volumes/live/31a2cf2b-96d8-4a45-7f54-678bc14b60ee/volume\\\" to rootfs \\\"/var/vcap/data/garden/graph/aufs/mnt/8da3238024d4ca66aa84fba1c718807b4cd727eb8ea11728325b3de7bd53e8ff\\\" at \\\"/var/vcap/data/garden/graph/aufs/mnt/8da3238024d4ca66aa84fba1c718807b4cd727eb8ea11728325b3de7bd53e8ff/scratch\\\" caused \\\"mkdir /var/vcap/data/garden/graph/aufs/mnt/8da3238024d4ca66aa84fba1c718807b4cd727eb8ea11728325b3de7bd53e8ff/scratch: permission denied\\\"\""
The permission denied error here seems to indicate some kind of setup failure, but I don't really know where to look. Any ideas?
Coming to work today, I find the build has run again, this time successfully. ¯\(ツ)/¯
I'm really not sure if this belongs here, with Concourse itself, or if I did something wrong, so sorry in advance.
We have concourse running on AWS with concourse-up, but pipelines are failing with this:
The permission denied error here seems to indicate some kind of setup failure, but I don't really know where to look. Any ideas?