Hi there!
Bug reports are pretty free-form; just replace this with whatever. You can also help us triage the issue by including steps to reproduce, expected results, and the actual result. Help us help you!
The following can also be handy:
I have deployed concourse cluster using bosh cli v2. I have pushed up my pipeline
resources:
- name: version
type: semver
source:
driver: git
uri: https://bitbucket.org/corvestadevops/devops.artifacts.git
branch: master
username: ((bitbucket-user))
password: ((bitbucket-password))
file: version
- name: resource-devops.ci
type: git
source:
uri: https://bitbucket.org/corvestadevops/devops.artifacts.git
branch: master
username: ((bitbucket-user))
password: ((bitbucket-password))
jobs:
- name: build-ci-repo
public: true
plan:
- get: resource-devops.ci
trigger: true
- put: version
params: {bump: minor}
- task: build-ci-repo
privileged: true
config:
platform: linux
image_resource:
type: docker-image
source:
repository: 038131160342.dkr.ecr.us-east-1.amazonaws.com/concourseci-build-java
aws_secret_access_key: ((MGMT_AWS_SECRET_ACCESS_KEY))
aws_access_key_id: ((MGMT_AWS_ACCESS_KEY_ID))
tag: 1.0.0
run:
path: sh
args:
- -exc
- |
echo 'Built version of ci repo'
This is to simply bump the version of the bitbucket repository. After I set-pipeline and created it I get this error runc create: exit status 1: rootfs_linux.go:42: preparing rootfs caused "permission denied" under - get: resource-devops.ci
I found this (https://github.com/concourse/concourse/issues/598) but I don't see how to add privileged to the -get. I have tried added it the params but this didn't do anything.


Thanks for reporting this @fewknow . You can find more conversation around the root cause of this problem in an issue posted under the concourse-lite repository: https://github.com/concourse/concourse-deployment/issues/46
Closing this issue for the same reason why the sister issue is closed, the stemcell conflicts with runc and there really isnt much we can do about it aside for suggesting that you go back to stemcell 3468.22 if possible
So aside from sticking on old stemcells what is the long term plan here? 3541.4 has the same issue.
Most helpful comment
Thanks for reporting this @fewknow . You can find more conversation around the root cause of this problem in an issue posted under the
concourse-literepository: https://github.com/concourse/concourse-deployment/issues/46Closing this issue for the same reason why the sister issue is closed, the stemcell conflicts with runc and there really isnt much we can do about it aside for suggesting that you go back to stemcell 3468.22 if possible