Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,334
Community Members
 
Community Events
184
Community Groups

Local runner: docker not found when running multiple steps or pipelines in parallel

Edited
Hannes Kuchelmeister
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 03, 2023

Hi,

on my local runner I face an issue when running either parallel pipeline steps (see image) or multiple pipelines in parallel. All steps but one that use docker end up returning bash: docker: command not found.

Screenshot 2023-05-03 112620.png

I was able to create a pipeline that reproduces the issue:

image: python:3.8.5-buster

clone:
lfs: true

pipelines:
custom:
custom-debug-pipeline:
- parallel:
- step:
runs-on:
- 'self.hosted'
- 'linux.shell'
clone:
enabled: false
script:
- echo "$PATH"
- docker container ls
- docker image ls
- step:
runs-on:
- 'self.hosted'
- 'linux.shell'
clone:
enabled: false
script:
- echo "$PATH"
- docker container ls
- docker image ls

 How can I solve this?

1 answer

1 accepted

0 votes
Answer accepted
Hannes Kuchelmeister
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 03, 2023 • edited

I found the issue myself. I had two runners tagged like this but only the non-HIL runner had docker installed.

Screenshot 2023-05-03 112620.png

I fixed it by tagging the docker runner with an additional docker tag

Screenshot 2023-05-03 133543.png

and then updating all pipeline steps that require docker to be using:

  runs-on: 
- 'self.hosted'
- 'linux.shell'
- 'docker'

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events