I've got a Pipeline build that requires running chroot to create a boot image and it appears to be failing because of some permissions thing.
I believe I read some where that chroot is not allowed in pipelines but I'm not sure where, can anyone point me to this documentation? And if it is true that chroot can't be run in a pipeline what is the recommended workaround to get my pipeline working?
Hello @Matt Schuckmann ,
I did some testing on my personal repository and was able to chroot in a directory inside the pipelines cloning dir.
That said, would you please share us the error that you are receiving when doing chroot on your pipeline ? What is the exact command you are executing ?
It would also help if you could share us the bitbucket-pipelines.yml file you have setup, so we can better understand the steps you are executing on your build. Please make sure to sanitize any personal information/credentials while copying the content of the file here.
Let us know in case you have any questions.
Thanks, @Matt Schuckmann .
Kind regards,
Patrik S
I: Base system installed successfully.
[2022-01-21 02:22:12] lb bootstrap_cache save
P: Saving bootstrap stage to cache...
[2022-01-21 02:22:13] lb chroot_prep install all-except-archives
[2022-01-21 02:22:13] lb chroot_devpts install
P: Begin mounting /dev/pts...
mount: /opt/atlassian/pipelines/agent/build/live/chroot/dev/pts: permission denied.
[2022-01-21 02:22:13] lb chroot_proc install
P: Begin mounting /proc...
mount: /opt/atlassian/pipelines/agent/build/live/chroot/proc: permission denied.
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Matt Schuckmann ,
In order to better assist you, I went ahead and created an internal support ticket for this particular case, with the e-mail you have associated with your community account.
With an support ticket, I will be able to access the builds and logs from our side, which will allow for faster and better troubleshooting for this issue.
You should have received an e-mail with the link of the ticket, but in case you was not able to find it, please let me know, so I can send it here. The support ticket will be visible only to you and Atlassian staff.
Thanks @Matt Schuckmann
Kind regards,
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.