Some Updates overwrite /etc/docker/daemon.json

jml79 · 31. Dezember 2023

When I run updates to OMV7 I often have the /etc/docker/daemon.json overwritten which kills my jellyfin and tdarr dockers. It is easy enough to run #nvidia-ctk runtime configure --runtime=docker to fix it but a small bug. At this point I am not sure if it is OMV7 updates that over write the file or OMV-Extras. I will monitor and report what updates cause the issue as more updates happen. So far I can only verify that the last update was openmediavault and openmediavault-kvm. I have tried installing a plugin to see if it was a general thing with the --allow-downgrades flag with apt-get but it didn't overwrite the daemon.json.

Last entry in /var/log/apt/history.log

Start-Date: 2023-12-31 02:26:19

Commandline: 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

Upgrade: openmediavault:amd64 (7.0-20, 7.0-21), openmediavault-kvm:amd64 (7.0.1, 7.0.2)

End-Date: 2023-12-31 02:26:51

chente · 31. Dezember 2023

Check this guide. There are some useful settings about this. I think it should work on OMV7 as well.

Beitrag

RE: [HowTo] Nvidia hardware transcoding on OMV 5 in a Plex docker container

******************************* OMV6 & OMV 7**************************************

If you are having issues with the new docker-compose-Plugin, read the comments regarding that issue.

Tested and running on:
- Linux Debian 11, Kernel 5.18.0-0.bpo.4-amd64, 5.18.0-0.deb11.4-amd64, 5.19.0-0.deb11.2-amd64, 5.19.17-1-pve, Linux 6.1.15-1-pve, Linux 6.2.16-11-bpo11-pve, 6.2.16-20-pve, 6.5.13-1-pve, 6.1.15-1-pve
- 6.9.1-1 (Shaitan), 7.0.1-1 (Sandworm)
- docker-ce 5:25.0.4-1~debian.12~bookworm
-…

chris_kmn

21. Mai 2022

ryecoaaron · 31. Dezember 2023

Zitat von jml79

When I run updates to OMV7 I often have the /etc/docker/daemon.json overwritten

Does the hint for Docker -> Docker storage on the Settings tab not make sense?

Install a kvm update did not cause this though. Any time you make a change in the Compose plugin in any tab, it will rewrite daemon.json unless you leave that field blank.

chente · 31. Dezember 2023

I think it would be positive to add this to the wiki. I haven't done it because I don't use Nvidia and I'm not sure how to write it.

I would appreciate if someone can post in this same thread (or in a PM if you prefer) a text to include in the wiki that explains this in a simple way.

ryecoaaron · 31. Dezember 2023

Zitat von chente

I think it would be positive to add this to the wiki. I haven't done it because I don't use Nvidia and I'm not sure how to write it.
I would appreciate if someone can post in this same thread (or in a PM if you prefer) a text to include in the wiki that explains this in a simple way.

Something like: "If you plan to customize docker and/or add settings to /etc/docker/daemon.json, leave the Docker storage field blank. This is very common for containers requiring nVidia hardware for transcoding/encoding."

chente · 31. Dezember 2023

Zitat von ryecoaaron

Something like: "If you plan to customize docker and/or add settings to /etc/docker/daemon.json, leave the Docker storage field blank. This is very common for containers requiring nVidia hardware for transcoding/encoding."

If you want to install docker on another disk, what happens if you leave that field blank? Can you configure docker on another disk by setting the new path and once configured leave the field blank? Will that respect the non-default docker route?

jml79 · 31. Dezember 2023

Well look at that. An ID-10-T error. I’ve cleared that field and I’ll keep an eye on it.

Thanks.

There is a very good, recent guide for OMV6 in the guides section. Can we make a post to add this detail to the thread or should I write a new guide and include this tiny change?

chente · 31. Dezember 2023

Zitat von jml79

There is a very good, recent guide for OMV6 in the guides section. Can we make a post to add this detail to the thread or should I write a new guide and include this tiny change?

I assume you are referring to the guide I linked in post #2. I thought that guide already included this configuration. If not I'm sure chris_kmn will offer to fill in whatever is needed.

ryecoaaron · 31. Dezember 2023

Zitat von chente

If you want to install docker on another disk, what happens if you leave that field blank?

If you leave the field blank, you are responsible for maintaining everything in /etc/docker/daemon.json. The plugin literally only creates this:

Code

{
  "data-root": "/var/lib/docker"
}

If you want to maintain a custom daemon.json AND use a different disk, you need to put whatever path you want in data-root. In the nvidia thread, you will still see data-root in the daemon.json for nvidia

Code

{
    "runtimes": {
        "nvidia": {
            "path": "/usr/bin/nvidia-container-runtime",
            "runtimeArgs": []
        }
    },
    "default-runtime": "nvidia",
    "data-root": "/var/lib/docker"
}

Zitat von chente

Can you configure docker on another disk by setting the new path and once configured leave the field blank?

I guess you could but it seems pretty simple to create the daemon.json yourself instead of relying on the plugin to create the initial one.

Zitat von chente

Will that respect the non-default docker route?

What do you mean by route?

chente · 31. Dezember 2023

Zitat von ryecoaaron

If you leave the field blank, you are responsible for maintaining everything in /etc/docker/daemon.json. The plugin literally only creates this:

This is starting to get complicated. That's why I haven't written all this on the wiki. If I don't experience it I won't understand it and that's why I ask for a text to publish. I hate writing something I haven't tried.

Zitat von ryecoaaron

What do you mean by route?

I guess I wanted to say "path", Google translation error, sometimes it translates "route" and other times it translates "path". I think that in Spanish those two words are synonyms. I'll have to keep this in mind in the future if they have different meanings in English.

ryecoaaron · 31. Dezember 2023

Zitat von chente

This is starting to get complicated. That's why I haven't written all this on the wiki. If I don't experience it I won't understand it and that's why I ask for a text to publish. I hate writing something I haven't tried.

It shouldn't be complicated. You leave it blank if you want to write the daemon.json. You put a path in it if you want daemon.json to only contain data-root. noobs shouldn't be leaving it blank. If they are because they are following a guide, it is that guide's job to explain that they need to set data-root if they don't want the default /var/lib/docker.

jml79 · 31. Dezember 2023

Zitat von chente

I assume you are referring to the guide I linked in post #2. I thought that guide already included this configuration. If not I'm sure chris_kmn will offer to fill in whatever is needed.

I was referring to this guide;

Thema

Using Nvidia Quadro P600 GPU in OMV 6+ for Tdarr and Plex Transcoding

I've sifted through at least 50 web posts on how to install the Nvidia drivers in order to get docker to recognize the driver and make Tdarr and Plex use the GPU to transcode my videos. I became more confused the more I read. Folks tend to make things more complicated than they need to be. This will probably work for other Nvidia cards as well.

I hope this helps others.

I've narrowed my install down to 4 major steps. I am not one to re-invent the wheel and even happier when I can mostly just cut…

reverendspam

23. November 2023

And it has 2 issues but I can’t add a post to help improve the guide. The first issue is the topic of this thread, the second issue is the most recent Tdarr builds require driver version 520 or higher and OMV6 ship with 470 so there is an extra step needed for Tdarr users to upgrade the base driver. OMV7 has 525 so doesn’t need the extra step. But the same 2 notes apply to the guide you posted as far as I can see. I love and hâte NVidia. Crazy fast and good transcoding but a PITA to get working well. My Intel and AMD transcode setups were way easier but much slower and the AMD was also much lower quality.

chente · 31. Dezember 2023

Zitat von jml79

And it has 2 issues but I can’t add a post to help improve the guide.

The threads in the guides subforum do not accept posts other than those of the author. You can quote the author here and he will see it when he enters the forum.

jml79 · 2. Januar 2024

Issue seems to be resolve. The latest update to OMV7 did not clear my custom .json file. I will post again if I have any other issue but I doubt it.

Thanks for the help.

Nefertiti · 20. Januar 2024

Zitat von ryecoaaron

It shouldn't be complicated. You leave it blank if you want to write the daemon.json. You put a path in it if you want daemon.json to only contain data-root. noobs shouldn't be leaving it blank. If they are because they are following a guide, it is that guide's job to explain that they need to set data-root if they don't want the default /var/lib/docker.

So far mine is blank because I am using a custom JSON for Nvidia, but I would love to move my docker folder out of the system drive, so now can I do that without being rewritten?

Because it is still saying "Leave blank to use a custom /etc/docker/daemon.json"

macom · 20. Januar 2024

Zitat von Nefertiti

So far mine is blank because I am using a custom JSON for Nvidia, but I would love to move my docker folder out of the system drive, so now can I do that without being rewritten?
Because it is still saying "Leave blank to use a custom /etc/docker/daemon.json"

The path to the "docker folder" is defined in daemon.json. It is called "data-root"

Nefertiti · 21. Januar 2024

Well I did something bad, In order to make room I started to remove an old docker file (what I thought) from a non system disk, and I did not rename it.

Now docker still running but portainer stays down I can still see the container, but they won't restart with error creating overlay2 mount to /var/lib/docker by the way var/lib/doker still have all the files in it specially overlay2!

How can I fix the mess

Nefertiti · 21. Januar 2024

I think I fixed it by running docker system prune -a was able to start portainer again,

all the stacks was there but with 0 container Just had to deploy the the stacks so far so good

Nefertiti · 22. Januar 2024

Zitat von ryecoaaron
If you want to maintain a custom daemon.json AND use a different disk, you need to put whatever path you want in data-root. In the nvidia thread, you will still see data-root in the daemon.json for nvidia
Code
{
    "runtimes": {
        "nvidia": {
            "path": "/usr/bin/nvidia-container-runtime",
            "runtimeArgs": []
        }
    },
    "default-runtime": "nvidia",
    "data-root": "/var/lib/docker"
}

Actually working perfect with the code of chris_kmn. Like I found out above just update the stacks in portainer don't even need to copy move the docker Folder

Code

{
    "data-root": "/srv/dev-disk-by-uuid-2e5438fd-633f-4658-82b0-dce4dccd3b97/docker",
    "runtimes": {
        "nvidia": {
            "args": [],
            "path": "nvidia-container-runtime"
        }
    }
}

If you are having issues with the new docker-compose-Plugin, read the comments regarding that issue.

Jetzt mitmachen!