interesting, a new container is showing up now. Can you reboot your system pls. Have a look to logs afterwards.
EDIT
one more to try to check who is using the volume
docker container ls --filter volume=portainer_data --format "table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Mounts}}"
after reboot no longer any portainer entries in the docker logs.
the command to check what is using the volume doesn’t return anything
docker container ls --filter volume=portainer_data --format "table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Mounts}}"
CONTAINER ID IMAGE NAMES MOUNTS
are you able to remove the volume now?
docker volume rm portainer_data
No it is in use…
docker volume rm portainer_data
Error response from daemon: remove portainer_data: volume is in use - [c6915cc05cf72928a85df77c39c5b0e3dd55a82aaeb0a594f1f961bc0c4dfa96]
WTF. let’s check who this container is
docker container ls --filter id=c6915cc05cf72928a85df77c39c5b0e3dd55a82aaeb0a594f1f961bc0c4dfa96 --format "table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Mounts}}"
That command does not return anything… do I misspell it?
docker container ls --filter id=c6915cc05cf72928a85df77c39c5b0e3dd55a82aaeb0a594f1f961bc0c4dfa96 --format "table {{.ID}}\t{{.Image}}\t{{.Names}}\t{{.Mounts}}"
CONTAINER ID IMAGE NAMES MOUNTS
I don’t get your system.
portainer_data can’t be removed because it is in use
we could stop all container and try to remove container ID starting c62e7be96e418fc455de0c
docker stop $(docker ps -aq)
docker rm c6915cc05cf72928a85df77c39c5b0e3dd55a82aaeb0a594f1f961bc0c4dfa96 --force
docker volume rm portainer_data
I stopped and renoved the container using the ID, now the dietpi script to uninstall worked.
I rebooteded and reinstalled portainer but I’m still getting the same error
2023/02/08 10:04PM FTL github.com/portainer/portainer/api/cmd/portainer/main.go:716 > failed starting tunnel server | error="listen tcp 0.0.0.0:8000: socket: permission denied"
Am I using an old image for this hardware? Shall I just reinstall my setup?
Daf
Yeah, your image is quite an old one running old kernel 4.9 still. If it is not that much hassle, you could use our current image having a way more up-to-date kernel version. Maybe give it a try on a spare SD card.
same issues and nothing would work. i uninstalled everything docker related and rebooted
while attempting to reinstall i got
│ E: Could not get lock /var/lib/apt/lists/lock. It is held by process 940 │
│ (apt-get) │
│ E: Unable to lock directory /var/lib/apt/lists/
eventually it installed. i rebooted and service logs say…
│ --containerd=/run/containerd/containerd.sock
│
│ Feb 17 05:10:33 DietDockerVM systemd[1]: Started Docker Application
│ Container Engine.
│ Feb 17 05:10:34 DietDockerVM dockerd[681]:
│ time=“2023-02-17T05:10:34.102671612-05:00” level=warning msg=“AppArmor
│ enabled on system but "apparmor_parser" binary is missing, so profile
│ can’t be loaded”
I am about to change it from dietpi managed to system but after that, i am just restoring my backup. this is a VM on proxmox. i even tried a fresh install of dietpi and updated before installing docker. it too had similar problems.
@applyscience
Your issue has nothing to do with the topic above. You are most probably hit by an issue of Docker software. This has nothing to do with DietPi. A simple forum search would have guide you to a workaround https://github.com/MichaIng/DietPi/issues/6126
@Joulinar I wanted to give my portainer a new update using reinstall 185 command, but it shows me this:
as always: any help is highly appreciated. thanks in advance!
The container name seems to be in use by another instance. Can you check following
docker image ls --all
docker container ls --all
Do you use any kind of software to update Docker container automatically?
here you go:
no, nothing that I am aware of that automatically updates anything.
Well you have quite some other Portainer container running. Like CE, EE and Updater. As you can see, the name /portainer is already used by your EE conatiner. Therefore it is conflicting with our install script. It would require a manuel adjustement to get an additional Poartiner running now.
Any reason for having all these veriants running?
I have no idea, sorry. 
I do not want to get an additional portainer, just update the current one. I thought portainer would handle my images (nginx, rustdesk and that is about it). I only use those two applications.
Portainer is just a gui / frontend to simplify Docker managent. If you don’t use the EE (Enterprise Edition), you should remove/drop it. CE (Community Edition) should be fine for private use.
I am afraid to lose any of my managed images (nginx and rustdesk) if I remove something. can’t I somehow update the portainer UI easily?
Dropping a conatiner should not impact any other container, as this is the basic idea of Docker, to separate the apps from each other. You should be able to remove Portainer EE and Portainer Update without any issue. And to be on save side, you could do a backup before.
last time the update command (reinstall 185) worked just fine. what are portainer EE and update for?
can I somehow see what portainer version is used currently to manage the docker containers?