Error Updating Kernel (linux-image-6.1.0-0.deb11.6-amd64 6.1.15) and applying changes in GUI - maybe linked to Docker-Compose AND Symlink

TiredHornet · 19. Januar 2024

Hi,

I am experiencing some trouble with OMV. I was in the changing the Docker-Compose "docker storage" path from the default "/var/lib/docker" to an SSD. Because I didn't want to use the long absolut path I though a Symlink would make things easier. I created a Symlink for the SSD and inserted a new path in "docker storage" (ssdm2/docker). From this point I am a bit fuzzy what I did next. Multiple tries to apply t hese setting a reverting back to the standard "/var/lib/docker" failed with errors. I then tried to install the OMV updates including "linux-image-6.1.0-0.deb11.6-amd64 6.1.15" which also didn't work.

The common part in the error messages that I saw was:

Code

Failed to create or replace /initrd.img: Is a directory at /usr/bin/linux-update-symlinks line 72.

The complete error messages can be found below. Any help or pointers on how to solve this are welcome.

Kind regards,

TiredHornet

Error from applying settings in docker-compose:

[TO LONG TO POST HERE]. I attached everything in the text fiel below.

Error from kernel update:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::="--force-confold" dist-upgrade 2>&1' with exit code '100': Reading package lists...

Building dependency tree...

Reading state information...

Calculating upgrade...

The following packages will be REMOVED:
  linux-image-6.1.0-0.deb11.6-amd64
The following packages will be upgraded:
  docker-ce docker-ce-cli docker-compose-plugin openmediavault
4 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 50.1 MB/52.5 MB of archives.
After this operation, 504 MB disk space will be freed.
Get:1 https://download.docker.com/linux/debian bullseye/stable amd64 docker-ce-cli amd64 5:25.0.0-1~debian.11~bullseye [13.7 MB]
Get:2 https://download.docker.com/linux/debian bullseye/stable amd64 docker-ce amd64 5:25.0.0-1~debian.11~bullseye [24.3 MB]
Get:3 https://download.docker.com/linux/debian bullseye/stable amd64 docker-compose-plugin amd64 2.24.1-1~debian.11~bullseye [12.1 MB]
Preconfiguring packages ...
Fetched 50.1 MB in 2s (21.3 MB/s)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 42214 files and directories currently installed.)
Removing linux-image-6.1.0-0.deb11.6-amd64 (6.1.15-1~bpo11+1) ...
Failed to create or replace /initrd.img: Is a directory at /usr/bin/linux-update-symlinks line 72.
dpkg: error processing package linux-image-6.1.0-0.deb11.6-amd64 (--remove):
 installed linux-image-6.1.0-0.deb11.6-amd64 package post-removal script subprocess returned error exit status 21
dpkg: too many errors, stopping
Errors were encountered while processing:
 linux-image-6.1.0-0.deb11.6-amd64
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1) in /usr/share/openmediavault/engined/rpc/apt.inc:226
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): Engined\Rpc\Apt->Engined\Rpc\{closure}('/tmp/bgstatusqs...', '/tmp/bgoutputuJ...')
#1 /usr/share/openmediavault/engined/rpc/apt.inc(229): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: Engined\Rpc\Apt->upgrade(NULL, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('upgrade', NULL, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Apt', 'upgrade', NULL, Array, 1)
#6 {main}

Alles anzeigen

chente · 19. Januar 2024

There's a warning about that here. https://wiki.omv-extras.org/do…mediavault-compose_plugin

Zitat

Warning
A symlink like /SSD/docker may not work here, it is preferable to use the full path. Example: /srv/dev-disk-by-uuid-861acf8c-761a-4b60-9123-3aa98d445f72/docker

TiredHornet · 19. Januar 2024

Zitat von chente

There's a warning about that here. https://wiki.omv-extras.org/do…mediavault-compose_plugin

Yeah, I read that a few minutes after my failed attempt. But I was not able to undo what I did and the system keeps giving me the same errors if I try to change something. Any ideas?

chente · 19. Januar 2024

The error in the kernel installation is probably not related to the error in the compose configuration. I can't read the compose error, that link asks for a password. It is better to attach a txt file in the forum.

chente · 19. Januar 2024

Have you tried setting the default path /var/lib/docker again?

TiredHornet · 19. Januar 2024

Zitat von chente

The error in the kernel installation is probably not related to the error in the compose configuration. I can't read the compose error, that link asks for a password. It is better to attach a txt file in the forum.

okay, i added a txt file in my first post and removed the link. Thankyou for your help.

chente · 19. Januar 2024

I guess it was your first time configuring the plugin. In that case docker is not installed yet. When you configure the necessary folders and apply changes, docker is also installed in the chosen path. The problem in this case is that the symlink is preventing this installation.

I would try modifying the docker installation folder to the default /var/lib/docker and applying changes. If you get an error again post it here. If everything seems to install and you have docker running, you can modify that path later to where you are interested.

TiredHornet · 19. Januar 2024

I already tried that and got the same error as before. I initially came from an old install with docker and portainer (from April 2023 before OMV changed to OMV-compose). If the fix isn't obvious it might be easier to just roll back to a by previously backed up installation and redo the whole whole docker-compose part.

chente · 19. Januar 2024

Before you get to that you can try simply uninstalling the compose plugin, rebooting and reinstalling the plugin. That should leave it ready to be configured again.

TiredHornet · 19. Januar 2024

When I try to uninstall a plugin I get the same error. I somehow managed to break a lot with my symlink as docker storage try.

chente · 19. Januar 2024

Zitat von TiredHornet

I somehow managed to break a lot with my symlink as docker storage try.

It seems. Maybe it would be easier to restore your backup since you have it.

chente · 19. Januar 2024

ryecoaaron I guess it's hard to detect whether the route set by the user is a symlink or a real route. So it might be a good idea to add a warning in that field in the GUI: "Do not use a symlink here."

Error Updating Kernel (linux-image-6.1.0-0.deb11.6-amd64 6.1.15) and applying changes in GUI - maybe linked to Docker-Compose AND Symlink

Jetzt mitmachen!

Tags

Warning
A symlink like /SSD/docker may not work here, it is preferable to use the full path. Example: /srv/dev-disk-by-uuid-861acf8c-761a-4b60-9123-3aa98d445f72/docker