containerd.io 1.7.24-1 on Debian 12 breaks glusterfs docker plugin

[troykelly]

Description of problem:
glusterfs for docker seems to pass mount arguments that are not allowed with containerd.io 1.7.24-1

The exact command to reproduce the issue:
Upgrade to conatinerd.io 1.7.24-1
Try and start the glusterfs docker plugin

The full output of the command that failed:

Expected results:
Docker starts with the plugin

Mandatory info:
- The output of the gluster volume info command:

- The output of the gluster volume status command:

- The output of the gluster volume heal command:

**- Provide logs present on following locations of client and server nodes -
/var/log/glusterfs/

**- Is there any crash ? Provide the backtrace and coredump

Additional info:

For those ending up here needing their docker + gluster to work quickly

export VERSION_STRING=5:25.0.5-1~debian.12~bookworm && \
export CONTAINERD_VERSION_STRING=1.7.23-1 && \
sudo apt-get update && \
sudo DEBIAN_FRONTEND=noninteractive apt-get -y full-upgrade && \
sudo DEBIAN_FRONTEND=noninteractive apt-get -y --allow-change-held-packages --allow-downgrades install docker-ce=${VERSION_STRING} docker-ce-cli=${VERSION_STRING} containerd.io=${CONTAINERD_VERSION_STRING} docker-buildx-plugin docker-compose-plugin && \
sudo DEBIAN_FRONTEND=noninteractive apt-get -y autoremove && \
sudo apt-mark hold docker-ce docker-ce-cli containerd.io

(We are locked to docker 25 because of swarm + IPv6 support - feel free to try your fave docker version)

- The operating system / glusterfs version:
Debian GNU/Linux 12 (bookworm)
glusterfs 11.1

Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration

[BarryLuijten]

@troykelly: In case you are also using this docker-volume-plugin, please have a look at this issue. I was able to rebuild the plugin and it's running fine now on containerd.io 1.7.24.