Still seem to have buster version of docker after OMV6 upgrade?

I actually did the upgrade a few weeks back and didn't see anything of note in the upgrade logs, but for some reason the docker-ce and docker-ce-cli packages seem to indicate that they are from buster and not bullseye (though it seems to be running ok AFAICT).

$ apt list --installed | grep docker

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

docker-ce-cli/now 5:20.10.16~3-0~debian-buster amd64 [installed,local]
docker-ce/now 5:20.10.16~3-0~debian-buster amd64 [installed,local]
docker-compose/stable,now 1.25.0-1 all [installed]
python3-docker/stable,now 4.1.0-1.2 all [installed,automatic]
python3-dockerpty/stable,now 0.4.1-2 all [installed,automatic]

$ apt list -a docker-ce
Listing... Done
docker-ce/now 5:20.10.16~3-0~debian-buster amd64 [installed,local]
docker-ce/bullseye 5:20.10.16~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.15~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.14~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.13~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.12~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.11~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.10~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.9~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.8~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.7~3-0~debian-bullseye amd64
docker-ce/bullseye 5:20.10.6~3-0~debian-bullseye amd64

The omvextras page in the dashboard shows the version as '5:20.10.16~3-0~debian-buster'. I'm wondering if something went wrong with these and whether there is some action I should take to address?

Thanks for the reply.

Yeah, that was going to be thing I tried first given that there shouldn't be too many other dependencies to deal with.

It did indeed fix the issue though I noticed that OMV6 seems to install docker-compose which I don't believe OMV5 did? It's actually a slightly older version (1.28.4) than I was running (1.29.2) and I decided to stick with the newer version as I have a script to refresh my containers based on:

docker-compose pull -q && docker-compose up -d

The older version always seems to restart the container with up -d even if nothing changed. I've found that useful for the linuxserver.io containers where you can specify the container tag in the compose file without the -ls# part and grab the between version image updates fairly simply without compose file changes.

I seem to have two copies of docker-compose. One in /usr/bin which claims to be 'version 1.25.0, build unknown' and one in /usr/local/bin (the one that the omvextras plugin installed?) which is 'version 1.28.4, build cabd5cfb'.

I believe that the output for the re-installation even explicitly stated that it was installing 1.28.4, it definitely wasn't 1.29.2.

$ apt list docker-compose
Listing... Done
docker-compose/stable,now 1.25.0-1 all [installed]
$ which docker-compose
/usr/local/bin/docker-compose

I renamed the one OMV installed to /usr/local/bin and replaced it with 1.29.2

Do we perhaps need the repo version installed for the dependencies? I looked to see what it would want to remove:

$ apt remove docker-compose
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
python3-attr python3-docker python3-dockerpty python3-docopt python3-importlib-metadata
python3-jsonschema python3-more-itertools python3-pyrsistent python3-texttable python3-websocket
python3-zipp
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
docker-compose
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 692 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

I don't think it should be too much of an issue to just leave things as-is though.

Yep, looks like it runs just fine if I remove docker-compose and autoremove the packages no longer needed.