Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
OneDev 10.4.0
|
Labels |
No labels
|
Issue Votes (0)
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
OneDev 10.4.0
|
Labels |
No labels
|
Hi Robin, I managed to get the kubernetes executor running with an image which was build from a kaniko job earlier in the pipeline.
The image contains tests, which are actually successful, but the executor hangs because of a permission error. The job also does not get cleaned up in the cluster and the jobs basically run forever in the build tab.
Here the log from the successful test job:
Seems like the CI systems wants to create some files where permissions and/or the folders are missing. For reference, here the Dockerfile which yields the base image for the tests:
I intend to run the tests as non-root and have the container non-privileged.
Is this intended and a mistake on my side or a bug?