Docker container volume mounts being attached as individual mounts with changed docker folder

[SpeeQz1]

Distribution

Mint 22

Package version

6.2.9

Graphics hardware in use

NVIDIA GeForce RTX 4060 Ti

Frequency

Always

Bug description

Usually when you start a docker container with binded volumes to your file system directory they won't appear as attached devices in the Nemo file manager or your desktop.

An unusual thing happens when you move your docker folder to a different place (for example /home/user). The volumes for docker containers get mounted to the file system and you visually can see them even though you aren't supposed to.

Note: My system uses 2 different partitions / and /home.

Steps to reproduce

To install docker: Docker Install Ubuntu

Provided bellow are commands to change the directory of the docker folder.

Stop docker:

sudo service docker stop
sudo systemctl stop docker.socket

Create new directory:

mkdir /home/$USER/docker

Add config to docker:

sudo tee /etc/docker/daemon.json << EOF
{
  "data-root": "/home/$USER/docker"
}
EOF

Copy files:

sudo rsync -aP /var/lib/docker/ /home/$USER/docker

Rename old docker:

sudo mv /var/lib/docker /var/lib/docker.old

Restart docker:

sudo service docker start

Remove old folder (unmounting volumes):

//If resource is busy

sudo grep /var/lib/docker /proc/mounts | awk '{ print $2 }' | tac | sudo xargs -n 1 umount 

sudo rm -rf /var/lib/docker.old

Run example docker containers like Penpot:

wget https://raw.githubusercontent.com/penpot/penpot/main/docker/images/docker-compose.yaml

sudo docker compose -p penpot -f docker-compose.yaml up -d

Expected behavior

When creating docker volumes they shouldn't be mounted as separate file system mounts and appear on both the Desktop or Nemo File manager.

Additional information

No response

[SpeeQz1]

I am not sure whether this should be reported in linuxmint or nemo so I went with Cinnamon.