All Docker Bamboo remote Agent Images for 9.2.x were updated recently, breaking changes
Asked by Phill Pafford:

I have a customer build using the base image for the bamboo remote agent, in docker hub

[https://hub.docker.com/r/atlassian/bamboo-agent-base/tags?page=3\&page_size=\&name=\&ordering=](https://hub.docker.com/r/atlassian/bamboo-agent-base/tags?page=3&page_size=&name=&ordering=)

I see that all versions for 9.2.x were recently updated

The base image was using

```
Ubuntu 22.04.1 (Jammy Jellyfish)
```

But now seems to be pulling

```
Ubuntu 24.04.1 (Noble Numbat)
```

and all the deps are breaking

How can I get the previous image?

```
atlassian/bamboo-agent-base:9.2.14
```

before the recent change?

<https://hub.docker.com/layers/atlassian/bamboo-agent-base/9.2.14/images/sha256-55a59daff1be04f92fe60d1eddc2e6d3c6a544e2671bf075abe7b2a47a2b5c61?context=explore>

Docker Image hash from 07/26/2024

```
26-Jul-2024 12:27:18	#5 [stage-1  1/44] FROM docker.io/atlassian/bamboo-agent-base:9.2.14@sha256:9be95195a34481a6af78d7b6fb5b80d30af37960909e750aee38793958ceedf726-Jul-2024 12:27:18	#5 resolve docker.io/atlassian/bamboo-agent-base:9.2.14@sha256:9be95195a34481a6af78d7b6fb5b80d30af37960909e750aee38793958ceedf7 done
```

Docker Image hash from 07/29/2024

```
build	29-Jul-2024 16:32:15	Digest: sha256:5311ba29f8d3f40c8dc8853740a024451ca11f7d99f65086c8aeb872bddcebd5build	29-Jul-2024 16:32:15	Status: Downloaded newer image for atlassian/bamboo-agent-base:9.2.14
```


Answers:
author: Eduardo Alvarenga
body: Good day, **Phil**,

Thank you for pointing that out. The Bamboo docker images and many other Atlassian products all depend on [Eclipse Temurin images](https://hub.docker.com/_/eclipse-temurin/) as a base image. Temurin images [have been refactored to ship with Ubuntu 24.04](https://github.com/adoptium/containers/pull/534/files), so our images followed that version.

We are working internally to pin our images to **Noble**, so future releases will not be affected by that change in the base image.

If you'd like to continue working with the **Jammy** version, pull the Docker image by its digest, as you have already identified. That will help you recover from your latest stable point, but it will also tie you to a specific version of the image, which will not receive any updates. Hence, we recommend you adjust your build process to adapt to the new **Noble** version.

You can also build your own image from scratch by cloning the [project](https://bitbucket.org/atlassian-docker/docker-bamboo-agent-base/src/master/). Customised images are not supported so you will have to read through the code and understand the process.

Cheers,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**

comments: author: Eduardo Alvarenga
body: Hey [@Phill Pafford](/t5/user/viewprofilepage/user-id/704705),

Good news!

We released **jdk11-jammy** and **jdk17-jammy** docker tags for the [Bamboo Agent Base docker image](https://hub.docker.com/r/atlassian/bamboo-agent-base).

That should help you with the earlier Ubuntu 22.04 version. Those *jammy* tags are one-offs, meaning they will not receive further updates, and you must plan your upgrade to the latest tags, **jdk11** or **jdk17,** that run on Ubuntu 24.04 (noble).

Regards,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**


author: Phill Pafford
body: HI [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) thanks for the explanation but for a released version you should not go back and update them with the same SEMVER, especially if there is a breaking change.

Thank you for the work around but this is disappointing as a consumer of Atlassian products.

<https://semver.org/>

NOTE: this also breaks what is documented

<https://confluence.atlassian.com/bamkb/how-to-upgrade-the-java-version-used-by-bamboo-1252329397.html>

Bamboo 9.2 is the LTS as well:

<https://confluence.atlassian.com/bambooreleases/bamboo-9-2-lts-change-log-1189803706.html>

So I'm not understanding how this is supported if you keep breaking backward capabilities


author: Eduardo Alvarenga
body: Hello [@Phill Pafford](/t5/user/viewprofilepage/user-id/704705)

Thank you for your concern. The version of Bamboo SEMVER has not changed. The Atlassian software remains the same as before. What changed was the Digest used by the base image, which is related to the docker tag and not a specific version. Due to an update in the Temurin Docker base image, our image ended up using that version once it was rebuilt.

We apologize for this, as it was beyond our control. To prevent this from happening again in the future if Temurin decides to update its base OS version, our images are now pinned to the Noble tag.

Kind regards,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**


author: Yevhen
body: [@Phill Pafford](/t5/user/viewprofilepage/user-id/704705) neither product binaries nor Java version have changed. The underlying OS and packages (especially packages) can change. We regularly rebuild and push images to get patched packages from Ubuntu repositories to mitigate CVEs. May I inquire about your use case? How exactly updating Ubuntu version impacted you?

Like [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) said, we'll be pinning base image tag to both jdk and ubuntu version (previously it was just jdk).

comments: author: Phill Pafford
body: we use the base image and extend it to add additional capabilities, some of the install process relies on specific packages at the OS level, since the OS was updated, the packages are not compatible.

I was not expecting the OS version to change in a tagged base image


Tags: bamboo-server

server