Currently, Bitbucket self-hosted runners using Docker-in-Docker (DinD) configurations require root access to function without errors, especially when running specific pipeline steps that rely on Docker pipes (e.g., atlassian/azure-storage-deploy). Using rootless Docker configurations leads to permission issues, warnings and an inability to mount necessary directories. This limitation blocks certain workflows for users who prioritize rootless setups for enhanced security or system constraints.

Solution:

Add support for rootless Docker-in-Docker (DinD) in Bitbucket self-hosted runners. This feature would ensure that rootless configurations are compatible with Bitbucket's pipeline steps, eliminating permission errors and network feature limitations.