Isolated container - Yes or No?

[Irina Litinskaja]

We are currently in the process of transitioning from Node.js 16 to Node.js 20. Our 'develop' branch successfully builds with Node.js 20, while our 'release' branch still relies on Node.js 16.

During the build process on the 'release' branch, we encountered an error indicating that the Node.js 16.x image lacks the necessary bindings for the version of node-sass we are using. Surprisingly, bindings for Node.js 20.x were found successfully in my build process, but not for Node.js 16.x.

Given that containers are designed to be isolated, we are puzzled by how this issue could occur. Any insights or suggestions on resolving this would be greatly appreciated.

Thank you for your assistance!

Best regards,
Irina

[Theodora Boudale]

Hi Irina,

If your Pipelines builds run on Atlassian's infrastructure or if you are using a self-hosted Linux Docker runner, then these builds use Docker containers.

For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in the build container, and then the commands of the step's script are executed. When the step finishes that Docker container gets destroyed. The containers are separate for each pipeline and they are also separate for each step of the same pipeline.

• Do these builds run on Atlassian's infrastructure or a self-hosted Linux Docker runner?
• Do you use pipelines that run on a branches definition, and do you have one for develop and another one for release branch?  
• If so, do you use a different image as a build container for the steps of each pipeline?
• I'm not sure what these bindings are. Are they preinstalled in the Docker image you use as a build container or do you download them during the build?

Kind regards,
Theodora