I am trying to setup runners for out bitbucket pipelines for our pipelines and happen to read documentation which lead me to these 2 questions
https://support.atlassian.com/bitbucket-cloud/docs/adding-a-new-runner-in-bitbucket/
and
https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/
Thank you for reaching out to the community.
Unfortunately, it is not highlighted in our documentation that you can run runners in the background through the Docker command.
However, it is possible to run runners in the background.
For the runners Docker command, you can add the -d flag and that will run the Docker container in a detached mode.
Sample runners Docker command:
docker container run -it -d -v /tmp:/tmp ........
After that, you should be able to run other commands on your server.
Now, if you'd like to monitor the runners container logs, you can use the below command:
docker logs <Runners container ID here> -f
To get the runners container ID, you can run docker container ls
I'll make sure to raise this to our documentation team and add it as an FAQ.
Meanwhile, do let me know how it goes.
Regards,
Mark C
Thank you for the response, understood how to handle it.
Can you also please explain the difference between
https://support.atlassian.com/bitbucket-cloud/docs/adding-a-new-runner-in-bitbucket/
and
https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Srikanth Mamidala
For the documentation here - Adding a new runner in Bitbucket
It is a guide on how you can set up Runners either in your specific repository or in a workspace level setting. When you add Runners in a workspace level, it can be used across your repositories whereas adding Runners in a specific repository will only make the runner available in that specific repository.
For the documentation here - Set up runners for Linux
It is a guide on how you can specifically set up Runners for the Linux environment and it also includes some optional best practices that you can implement in your self-hosted machine.
Let me know if you have further questions that I can help with.
Regards,
Mark C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark thanks for explaining. I’m sorry I may not have communicated my question well. So first documentation has a Linux runner setup as well which is different from 2nd document. I am confused over which runner setup is correct for Linux machines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Srikanth Mamidala
The first documentation is actually intended to be done on Bitbucket UI where you'll need to specify from which environment you'd like to run a Runner (e.g. Linux or Windows). This will also generate a Docker command where you'll need to copy and paste it into your chosen environment later on.
An example Docker command would be:
docker container run -it -d -v /tmp:/tmp ........
Whereas for second documentation, it is a guide for setting up your actual Linux environment (server) where you will run the Docker command above.
In summary:
Hope it helps and let me know if you have further questions.
Regards,
Mark C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So both documentation have to be done for security for the Linux runner setup ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Srikanth Mamidala
The first documentation is required while the second documentation is optional.
Regards,
Mark C
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.