Wow! This was brought up as far back as 2020!?!? Does Atlassian just not care about their customers or what?

Docker is NOT supported on RHEL moving forward! When will podman be supported? Is RHEL no longer a supported

platform for Atlassian Data Center products? We use docker-ce in our development environment, but that can't be used for

production workloads for obvious reasons. Maybe it's time to start looking at GitHub Actions...js

We have reached a point where we can't keep keep our Bamboo up to date without abandoning either Bamboo or Redhat.
CVE-2024-1597 's lowest fix Version is 9.2.12 (LTS) which requires Docker 17.07 or later but the only available version on RHEL is 1.13.1 in RHEL 7.9

Meanwhile no reaction on this issue, not even a timeline on when ( or if ?) podman will ever be supported...

Any news on the development of a plugin?

We cannot install docker by a workaround on redhat 8. Please give us a deadline on this feature

We have managed to find a way how to run Bamboo agents on CentOS Stream 9 with Podman as container runtime.

You'll need to setup rootless UID:GID mappings and modify Podman's default user namespace behaviour with --userns flag (or PODMAN_USERNS envvar).

• https://docs.podman.io/en/latest/markdown/podman.1.html#rootless-mode
• https://docs.podman.io/en/latest/markdown/podman-run.1.html#userns-mode

Also see https://www.redhat.com/sysadmin/debug-rootless-podman-mounted-volumes

wow, it is so frustrating, that no support answer ....  

If the RHEL is a supported OS ( it is ) , the podman should be as well ....

Has anyone ever figured a workaround for this? I don't know if Atlassian will fix this in time. RHEL9 has been announced for the next weeks.

After more than one year no response to this feature request and enterprise IT  is switching to Podman more and more. What is the answer from Atlassian and how Product Bamboo will deal with it ? I mean actual we are forced to setup an enironment with podman and bamboo and do our own test, completley unsupported by Atlassian. I am sure it will work, but i would feel better, if Atlassian is also having an eye on it. I mean, Redhad >= 8.x is not supporting Docker anymore for good reasons and switch to Podman (e.g. mitigating root access daemon). Highly appreciate here  a feedback

We also need this, podman supported in Bamboo, specifically 8.x    What is Atlassian's response?

Is there any update on this matter? RHEL 9 is already on the corner and we don't have any update on this. Docker is way longer deprecated and it's not viable anymore.

Docker is substituded by Podman in RHEL8.  We are forced to upgrade our Servers from Redhat/Oracle Linux 7. When there will be Podman supported by Atlassian ? Podman is the way forward on RHEL and in enterprise environments docker-ce is no real option anymore.

There are good reasons, why "yum related Distros" going that way. One of the main is to manage the typical "docker-root-issue" which is a PITA in Enterprise Environments.

Hope to hear from Atlassian - i am optimistic, that they are looking forward and try to reach bleeding edge status.

We are running Bamboo 7.1 on RHEL8.

Using Docker Task with Podman and podman-docker installed results in the following error:

Failing task since return code of [/usr/bin/docker logout <repo>] was 125 while expected 0

This error occurs because podman exit 125 if you weren't logged in when you try to log out while docker ignores this and exit 0.

I guess that Docker Task runs "docker logout <repo>" before "docker login <repo>" to make sure that the right user is logged in but since it doesn't handle an exit code 125 the Docker Task fails.

Please fix this issue, podman is the way forward on RHEL and a lot of enterprise customer use RHEL, docker is not an alternative.

Upgrading to RHEL8, we had to remove the standard distribution packages to install the deprecated Docker packages.

dnf remove podman buildah runc

I second that. It should be easy since Podman is a drop in replacement for Docker.

The problem is that Docker CE is broken on EL8, due to incompatibilities with containerd.io:

[root@atlassian ~]# dnf update
Updating Subscription Management repositories.
Last metadata expiration check: 1:32:18 ago on Fri 04 Sep 2020 04:56:07 PM -03.
Error: 
 Problem: package docker-ce-3:19.03.12-3.el7.x86_64 requires containerd.io >= 1.2.2-3, but none of the providers can be installed
  - cannot install the best update candidate for package docker-ce-3:18.09.1-3.el7.x86_64
  - package containerd.io-1.2.10-3.2.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.13-3.1.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.13-3.2.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.2-3.3.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.2-3.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.4-3.1.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.5-3.1.el7.x86_64 is filtered out by modular filtering
  - package containerd.io-1.2.6-3.3.el7.x86_64 is filtered out by modular filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

So this is really a necessity and no longer a "nice to have". EL (CentOS/RHEL) is the default OS on enterprise deployments.