I've created a separate filesystem on my zfs pool called docker. How do I get the Docker plugin to install onto this filesystem vs. the default /var/lib/docker directory?
I don't want it on my OS volume.
Thanks,
Install Docker onto ZFS Filesystem
-
Before you install docker change the path, /var/lib/docker becomes /<poolname>/<filesystem name> then click save, then install docker
-
before you move docker root to zfs do some googling and check out, if it works.
I remember there had been issues with that.
Is zfs now supported officially?
-
-
I remember there had been issues with that.
Is zfs now supported officially
Yes, there is a zfs storage driver, I was helping a user some time ago and we assumed the issue was related to docker on zfs, turned out to be something else, I have just installed docker on my test VM;
Code
Alles anzeigendocker info Client: Context: default Debug Mode: false Plugins: app: Docker App (Docker Inc., v0.9.1-beta3) buildx: Docker Buildx (Docker Inc., v0.7.1-docker) Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 20.10.12 Storage Driver: zfs Zpool: tank Zpool Health: ONLINE Parent Dataset: tank/docker Space Used By Parent: 31372 Space Available: 16279955846 Parent Quota: no Compression: lz4 Logging Driver: json-file Cgroup Driver: systemd Cgroup Version: 2 -
Screenshot from WinSCP;
-
I knew there was a reason why I deployed docker on another drive in OMV5 rather than zfs;
never did work out how what or why on the above, this after installing Portainer
-
-
ryecoaaron is there any way that the legacy filesystem can be hidden in the zfs GUI
-
Thanks for testing it out. Looks like the zfs storage driver creates a file system for each layer in the image.
Wait until you have some more containers running. There will be gazillions of fs.
-
s there any way that the legacy filesystem can be hidden in the zfs GUI
zfs filesystems only show up if they are imported. I will have to see what docker does but I think Zoki is right and there will be many.
-
-
Maybe it helps to force docker to use the overlay2 storage drive and not let it autodetect.
-
-
Or is this just an interface issue under OMV6
No, nothing to do with OMV, do a search for legacy filesystems on zfs after installing docker, as soon as tried this on my test VM I remembered why I went down adding another drive for docker and container configs.
-
I'm a newbie, how do you do that?
Docker has excellent docs: https://docs.docker.com/storag…edriver/overlayfs-driver/
-
Docker has excellent docs
I agree, and having found an article that suggests using another storage driver, I've just tested that following the link and adding the storage driver to the daemon json file, but unfortunately this doesn't work as docker still uses the zfs storage driver
-
-
Too bad, so OP has no other chance than fitting another drive in his case.
-
you can format a ZFS volume as ext4 to workaround this issue.
-
-
Alles anzeigen
I already found that document, however I don't understand the following instructions..
"If you want to use a separate backing filesystem from the one used by
/var/lib/, format the filesystem and mount it into/var/lib/docker. Make sure add this mount to/etc/fstabto make it permanent."It appears that even though I specified /Pool1/Docker for the Docker storage, which is my zfs filesystem, it still installed the same file structure in the /var/lib/docker folder with the addition of a overlay2 folder. There are no containers in this structure, they are in /Pool1/Docker.
It looks like it's using /var/lib/docker for its install and /Pool1/Docker for storing containers?
They use /var/lib/docker as synonym for the docker-root. You can either mount a different file system to /var/lib/docker or move it by changing /etc/docker/daemon.json (which you did using the plugin).
What you see in /var/lib/docker is what has been placed there in the initial docker install before you moved it to your pool.
-
They use /var/lib/docker as synonym for the docker-root. You can either mount a different file system to /var/lib/docker or move it by changing /etc/docker/daemon.json (which you did using the plugin).
What you see in /var/lib/docker is what has been placed there in the initial docker install before you moved it to your pool.
OK, well that makes sense.
So the bit about using the overlay2 driver implies using an ext4 partition?
It appears as soon as you move the install to a zfs volume it switches to using a zfs driver.
All of my drives are part of zfs Pool1. Can I create a separate filesystem off of that and format it as ext4? if so, how?
Thanks,
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
