bash: docker: command not found

[Harshad Prajapati]

Our Bitbucket pipeline was working fine, but in the past few days, it has started failing with the following error:

bash: docker: command not found

Runner Type: Self-hosted

Runner labels: self.hosted, linux

Runner version: current: 3.11.0

[Jim Knepley - ReleaseTEAM]

Hi @Harshad Prajapati 

Taken at face value, that error indicates that the OS can't find the "docker" executable in the search path. Either the search path has changed and doesn't reference the location of the executable, or Docker isn't installed on the build instance.

[Harshad Prajapati]

Thanks for the input. Could you suggest how I can debug this issue? Any specific checks or logs I should look into?

[Harshad Prajapati]

Also, When I manually deploy by connecting to the machine, Docker works fine, and I don’t encounter this issue.

[Jim Knepley - ReleaseTEAM]

First, find the docker binary. When you log in manually, use the "which docker" command to identify the full path that the executable is in.

In your pipeline, either update the path to include the directory where the docker executable is installed or reference docker by its full path name from above.

[Harshad Prajapati]

Added Path as per screenshot 

End up with another errors

[Jim Knepley - ReleaseTEAM]

What, exactly, did you add to the path?

All of those binaries on my Ubuntu 24 lab machine are in the /usr/bin directory. That's a very normal location for things to live in, so it's probably OK to include that in the path when running a pipeline.

[Harshad Prajapati]

I've added screenshots already. PATH = /usr/bin/docker

[Harshad Prajapati]

I've added /usr/bin as well as you suggest, but still same error 

[Harshad Prajapati]

Any update ?

[Harshad Prajapati]

@Jim Knepley - ReleaseTEAM 

[Jim Knepley - ReleaseTEAM]

I don't have anything more to add without hands-on troubleshooting.

[Harshad Prajapati]

Thanks