I’ve got some problems after Upating from Debian Stretch to Debian Buster, and from Debian Buster to Debian Bullseye, since than my Docker containers are not running anymore.
I tried to reinstall Docker, but I get errors something with “Lua”, have no clue what this is.
It says I have to configure it, so I’ve tried “sudo dpkg --configure -a”, after this I get:
lua5.2 (5.2.4-1.1+b3) wird eingerichtet ...
update-alternatives: Fehler: Alternativen-Link /usr/bin/lua wird bereits von lua verwaltet
dpkg: Fehler beim Bearbeiten des Paketes lua5.2 (--configure):
»installiertes lua5.2-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurü
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von luarocks:
luarocks hängt ab von lua-any; aber:
Paket lua-any ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes luarocks (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
lua5.3 (5.3.3-1.1+b1) wird eingerichtet ...
update-alternatives: Fehler: Alternativen-Link /usr/bin/lua wird bereits von lua verwaltet
dpkg: Fehler beim Bearbeiten des Paketes lua5.3 (--configure):
»installiertes lua5.3-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurü
Fehler traten auf beim Bearbeiten von:
lua5.2
luarocks
lua5.3
I get the same errors when trying to “–force-remove” Lua.
I’ve also installed the previous version 5.2 and 5.1.
As you probably can see, I have no clue what the heck is going on, I just want my Docker containers back running
I should have stayed on Debian Stretch, everything was working with this release
Can somebody please help? Which logs do you need, to point me in the right direction?
hope you have done a backup before, that could be used to restore your system. Did the issue happen on the update to Buster already? Was everything working on Buster?
If you don’t need the lua package, you could try to purge it
I’ve done a backup, nevertheless I am not sure if it’s complete, but I guess it it is. It just took very long, I let it run over night.
I have updated right away from Buster to Bullseye, as I’ve read the recommendation from DietPi to update to Bullseye because of the newest security updates.
With “apt purge lua”
I get the same error, like I’ve copied in my post.
with “apt purge lua*”
I get the error luarocks-3.8.0 can’t be found
From the first error message, what does Lua want if it says lua5.3 and lua 5.2 needs to be configured?
What exactly I have to configure, with which command?
Update:
I have realized now the backup didn’t work “backup not found”, but I am 100% sure that I run the backup command.
Update2:
I get rid of this lua “virus” by typing the apt purge command with any lua package one after another, like apt purge lua-any, apt-purge lua5.3, apt purge luarocks and so on. Nevertheless this doesn’t fix the problem, that docker doesn’t work anymore since the Bullseye update. Tried also reboot and reinstall of Docker with dietpi-software reinstall
Update3:
I found out that Docker buster release was installed, I’ve updated it to the newest Docker bullsye version. But this also doesn’t help, when running “sudo docker run hello-world” I get the error message
docker: Error response from daemon: OCI runtime create failed: cgroup namespaces aren’t enabled in the kernel: unknown.
ERRO[0001] error waiting for container: context canceled
Linux dietpi 4.4.192-rockchip64 #1 SMP Tue Oct 8 18:39:24 CEST 2019 aarch64 GNU/Linux
ROCK64 (aarch64)
I’ve updated to DietPi Beta yesterday, but the error was also in the stable version.
I am also not sure, how I can update the kernel and which might work with arm64 device.
With the command dpkg -l | grep linux-image I get:
ii linux-image-4.4.126-rockchip-ayufan-239 0.6.44 arm64 Linux kernel, ver sion 4.4.126-rockchip-ayufan-239
ii linux-image-5.1.0-1114-ayufan-g097e5be61be4-dbg 5.1.0-1114-ayufan arm64 Linux kernel debu gging symbols for 5.1.0-1114-ayufan-g097e5be61be4
ii linux-image-5.9.0-1146-ayufan-gab09e252a729 5.9.0-1146-ayufan arm64 Linux kernel, ver sion 5.9.0-1146-ayufan-gab09e252a729
ii linux-image-rockchip64 5.98 arm64 Linux kernel, ver sion 4.4.192-rockchip64
Uii, this is an old Ayufan based image and related old kernel. Though they are still maintained as can be seen by the newer kernel packages installed already, and even Linux 5.13 builds are available in theory: https://github.com/ayufan-rock64/linux-mainline-kernel
If you find some time to transfer you data and configs, then I’d still recommend to flash our new ROCK64 Bullseye image, based on current Armbian kernel, where we better know the setup, repository, what/how things work etc.
If you want/need to stay with this image, looks like we can also upgrade the kernel, but let’s see how it is setup currently:
uname -a
ls -al /boot
apt show linux-image-rockchip64
cat /etc/apt/sources.list.d/*.list
Actually I would prefer just to update the kernel (to 5.13), but don’t know how.
But if it’'s easy to backup and migrate Docker and my containers to the new ROCK64 Bullseye image you’ve mentioned I would also consider this.
Basically I have not really changed anything in Dietpi and software I have only installed samba server, docker, dropbear and webmin. That’s it.
Okay this is pretty confusing. It seems there are Armbian kernel + boot config and Ayufan kernel mixed on your system. Did you manually added kernel packages or other repositories in attempt to get a newer version? I see the disabled but present Armbian repository entry. I worry about e.g. the Linux image and device trees being linked to the Armbian 4.4.192 kernel, which also is the one loaded, but the initramfs is linked to Ayufan’s Linux 5.9 based uInitrd. When cleaning this up, we need to be careful to not render the system unbootable since e.g. I have no idea which bootloader is really in use. But actually it looks like it is originally an old Armbian image, while the Ayufan repository has been added later for unknown reasons, probably by you in attempt to get a newer kernel?
The post you deleted btw contained some helpful information. Why did you delete it?
However, let’s start with some safe cleanup of those kernel images which are definitely not in use:
And from your deleted post, I saw that you have added the experimental Debian repository, which I would remove as long as you do not know exactly what the impact of this is. So let’s assure the standard Debian Bullseye repo parts are added only:
cat << '_EOF_' > /etc/apt/sources.list
deb https://deb.debian.org/debian/ bullseye main contrib non-free
deb https://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb https://deb.debian.org/debian-security/ bullseye-security main contrib non-free
deb https://deb.debian.org/debian/ bullseye-backports main contrib non-free
_EOF_
apt update
If it indeed turns out to be an Armbian image, or at least with a compatible partition table, then we can simply install the newest Armbian kernel (5.10) and U-Boot.
I’ve added some newer kernel packages from ayufan, but I was not able to upgrade the kernel. At least I wanted a kernel with version 5.x, which could handle cgroup namespaces. Also tried a workaround with a namespace command loaded at boot, but this also didn’t work.
Sorry for deleting the post, was kinda frustated and thought what I did there had made not much sense anyway and didn’t want to spam the forum too much
In the meantime I thought about the second option again, to start with a new Dietpi bullseye image. Maybe there’s to much mixed up with the kernel/system now. And probably I’ve already wasted to much time trying to upgrade the kernel or to workaround this cgroup namespace errorr. In this time I might had already a running system, if I had started with a fresh install.
Backing up the docker containers was quite easy, but from my linux eperience so far, I’m afraid, there will be still something which will prevent to restore them properly… let’s see.
Okay so then I’m pretty sure it’s an Armbian image which makes the kernel upgrade very easy. But please run the commands provided above for initial cleanup and to get some more info assuring that what I think is true .
Sorry, saw your post to late. Flashed the newest Dietpi Bullseye image and everything is back to normal now, I should have done it this way in the first place.
The last kernel which was active was 4.192 from ayufan, don’t know about Armbian.
Thanks for your help.
.