Self hosted Runner error: no such container system_auth-proxy

[Eduardo GF]

Over the last few days we have been seeing multiple pipeline failures due to:

Status 404: {"message":"No such container: d3d13ac8-026f-5d95-aeca-27edbf06bfaf_d72f0c61-aab0-41f9-80d8-2167754d96bc_system_auth-proxy"} Refer to the Troubleshooting runners document for help resolving the issue.

After a rerun of the pipeline everything tends to be working, even with the same runner.
Runners are version current: 3.33.0

[Ben]

Hi @Eduardo GF 

I can see you belong to a Premium workspace. To troubleshoot this further, we'll need a formal support ticket to gain access to your environment and troubleshoot further.

May you please raise a support ticket by selecting Technical issues & bugs and selecting Bitbucket Cloud as the product? Ensure you use the paid workspaceID:

• https://support.atlassian.com/contact

If you encounter difficulties raising a ticket, please let me know your timezone so I may raise one on your behalf with the team that operates during your working hours.

Cheers!

- Ben (Bitbucket Cloud Support)

[Arkadiusz Wroblewski]

Hey and welcome to the Community @Eduardo GF 

this matches a known Bitbucket bug (BCLOUD-24057) causing that "No such container" error. Atlassian is rolling out a fix, confirming your 3.33.0 runner isn't the problem.

For now, try rerunning the step, increasing runner resources, or reducing disk contention. I suggest watching the ticket and opening a support case if this blocks production.

Best,

Arkadiusz 🤠☀️