Any hints to save my portainer images on my previous docker ?
[Solved] RPi 32 bits, docker and portainer (no Rollback from 6.9 to ???)
-
You can make a backup of the Portainer settings.
Or just save the compose files, if you are using those in Portainer.
Additionally make a backup of your docker volumes for config and appdata if they are on the OS filesystem,
-
I'd need a little bit help since portainer and docker wont start anymore
-
-
I'd need a little bit help since portainer and docker wont start anymore
Only saying something doesn't start, helps nothing.
What have you done PRIOR to that?
On what system is this happening?
Outputs inside CODE boxes of:
systemctl status docker
docker ps -a
-
-
pi@raspberrypi:~ $ systemctl status docker
You need to run those as root OR with sudo
sudo systemctl status docker
sudo docker ps -a
dpkg -l | grep docker
If it's erroring on the security repo, you can try to disable it temporary but this is a safety risk, so do it at your own risk.
Search ALL the .list files under /etc/apt and comment the line/s where it show the http://security.debian.org/debian-security bullseye-security
After, run and post the output of:
sudo omv-upgrade
-
Display More
You need to run those as root OR with sudo
sudo systemctl status docker
sudo docker ps -a
dpkg -l | grep docker
thanks for yours answers
Same output
and
Codepi@raspberrypi:~ $ dpkg -l | grep docker ii docker-buildx-plugin 0.17.1-1~debian.11~bullseye armhf Docker Buildx cli plugin. ii docker-ce-cli 5:27.3.1-1~debian.11~bullseye armhf Docker CLI: the open-source application container engine ii docker-compose-plugin 2.29.7-1~debian.11~bullseye armhf Docker Compose (V2) plugin for the Docker CLI. ii python3-docker 4.1.0-1.2 all Python 3 wrapper to access docker.io's control socketIf it's erroring on the security repo, you can try to disable it temporary but this is a safety risk, so do it at your own risk.
Search ALL the .list files under /etc/apt and comment the line/s where it show the http://security.debian.org/debian-security bullseye-security
After, run and post the output of:
sudo omv-upgrade
Here the sources.list, no security
Codedeb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi # Uncomment line below then 'apt-get update' to enable 'apt-get source' # deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi -
Here the sources.list, no security
There are a lot more under it.
ls -al /etc/apt/sources.list.d/
OR
sudo grep -r security /etc/apt/*
Same output
andIt's missing the docker-ce PACKAGE
Try to install it with sudo apt install -f docker --dry-run (if all goes correct, do it again without the --dry-run argument)
If it doesn't work, then you better consider the containers lost and star over on a proper 64Bit rig.
-
-
I think it's impossible since the bullseye has no 32 bits raspbian package
Don't understand this comment.
Bullseye has ALL versions available:
But can I run a docker with no compose ?
Again, don't understand this.
You can run a docker run line without having docker-compose YML.
Unless you mean something else so, please explain.
I manage to install docker, now I have ot run it with an image where all my portainer image were
So, does this mean that you can now make the backup that you wanted to do?
-
-
1. Soma wrote that 32 bits system is no more compatible with omv (I'm a bit lost here I'm afraid)
I never said that.
I said that I don't know how to bypass the error you are having with the failed GPG signature on the bullseye-security repo.
I asked you for some outputs on post #29 but you haven't replied with any.
I'm not in front of your system so, I can only guess what is going on.
2. How to start the docker image that omv created by default ?
Docker runs on the host independent of OMV.
If using the openmediavault-compose plugin, you only have a front-end to control it (same as having portainer).
Since you said you wanted docker running to make backups of the containers, I gave you a solution to have docker running.
If you are just forcingly trying to run the openmediavault-compose plugin, start by making sure that it's installed:
sudo apt install -f openmediavault-compose
As for the rest
Post ALL the commands and their outputs inside CODE boxes:
dpkg -l | grep openm
dpkg -l | grep docker
sudo grep -r security /etc/apt/*
sudo omv-aptclean
sudo omv-aptclean repos
-
-
ii openmediavault-compose 6.11.3
Openmedia compose is installed.
Do you see it on OMV webgui?
sudo grep -r security /etc/apt/*
/etc/apt/sources.list.d/openmediavault-os-security.list:deb [signed-by=/usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg] http://security.debian.org/debian-security bullseye-security main contrib non-free
/etc/apt/sources.list.d/openmediavault-os-security.list:deb-src [signed-by=/usr/share/keyrings/debian-archive-bullseye-security-automatic.gpg] http://security.debian.org/debian-security bullseye-security main contrib non-free
You can try this AT YOUR OWN RISK:
Delete that file with sudo rm -f /etc/apt/sources.list.d/openmediavault-os-security.list
Run and post the output of
sudo omv-aptclean
sudo omv-upgrade
-
My Saviour !!!!!
it worked !
Im' such a noob that I did'n,t undrstood why the 32 bits version was NOT a problem ? could you take another minute to explain ?
NB : Already Donate to OMV, should I donate to the plugin seciton ?
-
-
could you take another minute to explain ?
32bits systems have been deprecated more and more for the last years.
This has caused a lot of issues with the repos signatures (especially on armhf) and you can see it on the forum.
Hence the advice to use arm 64bits since it would solve all issues.
NB : Already Donate to OMV, should I donate to the plugin seciton ?
Well, if you can, please do.
OMV core is the work of one developer (votdev) and the plugin (omv-extras) section is the work of another developer (ryecoaaron) so it's two seperate section's.
Thank you
-
And more and more docker containers (images) are not available for 32bit.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
