Seeing permission errors running tests in `toolkit` folder in onebranch pipeline.

[aditimalladi]

Seeing permissions errors running upstream toolkit tests in Azure Devops pipelines.
Snippet of the failing tests:

ERRO[0000][safechroot_test] Mount of () to (/tmp/TestInitializeShouldCreateRoot3147199148/001/TestInitializeShouldCreateRoot/dev) failed. Error: operation not permitted 
WARN[0000][safechroot_test] Error creating mountpoints for chroot        
--- FAIL: TestInitializeShouldCreateRoot (0.00s)
    safechroot_test.go:60: 
            Error Trace:	/__w/1/s/.pipelines/toolkit/tools/internal/safechroot/safechroot_test.go:60
            Error:      	Received unexpected error:
                        	operation not permitted
            Test:       	TestInitializeShouldCreateRoot
    safechroot_test.go:65: 
            Error Trace:	/__w/1/s/.pipelines/toolkit/tools/internal/safechroot/safechroot_test.go:65
            Error:      	Should be true
            Test:       	TestInitializeShouldCreateRoot
ERRO[0000][safechroot_test] Mount of () to (/tmp/TestCloseShouldRemoveRoot3825882244/001/TestCloseShouldRemoveRoot/dev) failed. Error: operation not permitted 

We use the azurelinux toolkit to build a RPMS package to be published.
As these tests are already maintained and run upstream, is there a flag that we can pass to skip running all these tests?

[dmcilvaney]

Hey @aditimalladi , I'm assuming you are using a OneBranch container build environment here. There was a change in that environment (removing /.dockerenv) that broke some detection logic we use. This detection logic is fixed in 2.0 here and in 3.0 here. The 3.0 fix is in the latest stable release already, but I'm assuming you are seeing this failure in 2.0 since that release is in progress right now.

Fixes (in order of difficulty)

• Wait for the 2.0 release
• Grab those commits and manually apply them to your toolkit
• Place the file /.dockerenv file manually before the build via an extra step in the pipeline

Unfortunately, the actual tools will fail in the same way even if the tests are disabled.

Bug: https://microsoft.visualstudio.com/OS/_workitems/edit/55008881

[aditimalladi]

Thanks @dmcilvaney . Yes, we are using OneBranch and 2.0.
Would this be fixed post the release of 2.0? What is the timeline for the release?

[dmcilvaney]

The release is in progress right now, so should be soon(tm).

[dmcilvaney]

@aditimalladi https://github.com/microsoft/azurelinux/releases/tag/2.0.20241208-2.0 should fix this.