Don't use local Docker Volumes

[@MichaelWDietrich]

Great walkthrough and howto. Thanks for that. Nevertheless, small criticism at this point. NFS volumes and snapshot backups on the target NAS IMHO do not replace an application-based backup. Of course (for example in the event of a power failure but also due to other technical and organizational problems) the volumes on the NFS can be destroyed and become inconsistent in the same way as those on the local machine. This is even more likely because the writing process on the NFS relies on more technical components. That's why I also do and highly reccomend application-based backups with at least the same frequency. If the application's backup algorithm is written sensibly, it will only complete the backup after a consistency check and then it is clear that at least this backup is not corrupted and can be restored without data loss.

[@HoshPak]

Some food for thought... Most NAS systems have 2 network interface. You could attach the NAS directly to the server on a separate VLAN and optimize that network for I/O, enabling jumbo frames etc. That basically makes it a SAN without the redundancy. Using iSCSI instead of NFS is also an option and might be preferred for database workloads I assume.

[@kamilkroliszewski689]

Exactly, we used NFS as storage for databases and it handled not very good. Sometimes you have locks etc.

[@christianlempa]

Thanks for your experience guys, I have just a little experience with it. FYI, I was playing around with Jumbo Frames on a direct connection between my PC and TrueNAS, worked pretty well. VLANs is a topic for a future video as well :D So stay tuned!

[@macntech4703]

I also think that iscsi might be the better choice compared to nfs or smb. at least in a homelab environment.

[@HoshPak]

@@christianlempa I've been though that endeavor, just recently. When I searched for tagged VLAN on Linux, the documentation was hopelessly outdated referring to deprecated tools. My advice: disable anything that messes with net devices even remotely (i.e NetworkManager) and go straight for systemd-networkd. I've built a VLAN-aware bridge which functions just like managed switch. Virtual NICs from KVM attach to it, automatically as well as Docker containers. This is also a pretty good way to use tagged VLAN inside VMs which on KVM is hard to use, otherwise. If you'd like some help at the beginning, let me know. We will get you started. :)

[@gordslater]

last time I did this I had best results using ATAoE, it's not used very much nowadays but is very fast for local links (it's non-routable but ideal for single-rack use)

[@NathanFernandes]

Brilliant! I was just looking at something like this today, but instead I was trying mounting my synology as a cifs volume, nfs is so much easier and this video helped me set it up under 5mins. Thank you!

[@christianlempa]

Thanks! :) You're welcome

[@therus000]

is it work for you? i just do as instructions. but cannot great subfolders as a volume's. i got error 500. i try add map root to admin. but got same problem. error500. but if i make volume in the root of nfs folder. it work. but im not comfortabe with that. may be any help. i got dsm7

[@a5pin]

@@therus000 Hey I have the same problem, did you manage to resolve this?

[@ColoredBytes]

I followed this for my WindowsNAS to share to docker and this is so much easier then doing host level mounts. Thank you soo much

[@christianlempa]

You’re welcome :)

[@ColoredBytes]

@@christianlempa Hello again , I was wondering if by chance you knew how to specify this in a docker compose file im trying to make a template and this seems to be only my stopping point atm

[@ninadpchaudhari]

Btw, one point I need to add here: doesn’t mean you don’t need to have backups. Having redundant storage over NFS is nice. But do ensure you still have restorable backups in addition to this. There can be many things that can go wrong here, your FS might get corrupt in case there was a network problem while writing a bit or the raid fails etc etc.

[@christianlempa]

Absolutely! Great point, and I might explain this in future videos :)

[@gullijons9135]

Good point, "RAID is not backup" is something that really needs to be hammered home!

[@anthonyjhicks]

This was awesome. Perfect timing as exactly the next step I wanted to make with my volumes on Portainer.

[@christianlempa]

Haha cool :D Glad it was helpful

[@blairhickman3614]

I wish I found this video last week. It would have saved me hours trying to mount a NFS share on my Ubuntu server. I ran into the user permission issue also and it took a lot of searching to find the answer.

[@christianlempa]

Glad it was helpful bro 😎

[@fx_313]

Hey! Thank you very much for this. Can you also give an example on how to use an NFS mount in docker-compose / Stacks in Portainer? I've spent the last couple of hours trying and googling but wasn't able to find a real answer or constant examples on how to do it.

[@ColoredBytes]

I'm having the same issue lol , did you by chance find a way to do this?

[@ercanyilmaz8108]

You can also run docker containers in TrueNas itself and connecting to the NFS locally. If I'm right the writes can then handled synchroniously. This gurantees the data integrity.

[@haxwithaxe]

Glusterfs works really well for small files or small file transfers as well. Edit: I've since been told databases don't scale well on glusterfs. IDK how much experience that person has with glusterfs but they have enough experience with k8s for me to accept it until I can test it. Works great for the really small stuff I do in my home lab though.

[@christianlempa]

Oh yeah that's an interesting topic

[@NicoDeclerckBelgium]

True, but you have Galera Cluster for MySQL/Mariadb or just replication in PostgreSQL. But I get that the real problem is the 'other' dozens of databases. They can still be on a centralised storage, but as you say they don't scale well ...

[@steverhysjenks]

How do you replicate into docker compose? I get these steps and its graat for me to understand manually the steps. I'm not convinced my compose is working correctly for NFS. Love to see this explanation converted into a docker compose example.

[@jmatya]

Many of the big datacenter also use Fibre channel based storage, network attached can be slow and subject to tcp congestion and package loss, whereas fc is guaranteed delivery.

[@marcoroose9973]

When migrating cp -ar maybe better as it copies permissons, too. Nice video! Need to figure out how to do this in docker-compose.

[@christianlempa]

Oh great, thank you ;)

[@ansred]

Would be appreciated if you figured out and share how to use docker-compose on Portainer. That would be really handy!

[@ronaldronald8819]

I am triggered into high gear learning mode by all of this. The aim is to set up a home assistant server. ha runs in docker and stores its data in local volumes. I am no fan on having my data all over the place so this video solves that problem. So next step is to get my hands dirty and hope i do not get to many errors that exceed my domain of knowledge. Thanks!!

[@christianlempa]

You're welcome! :)

[@iggienator]

Danke, das hat mir weitergeholfen 👍

[@christianlempa]

Freut mich! :)

[@G00SEISL00SE]

I have been stuck for weeks with an nsf volume not mounting right inside my containers. First I couldnt edit the created files. Then I could but couldn't create new ones. This fixed both my issues thanks going to set up my shares like this moving forward.

[@rino19ny]

it's the same thing. a storage server can also crash. and you have a complicated setup with a NAS storage. either methods you select, a proper backup is best.

[@ilco31]

this is great to know -i am currently looking into how to back up my more info sensitive docker containers -like vaultwarden or nextcloud -great video

[@Clarence-Homelab]

I mainly use bind mounts for my persistent docker storage (had MAJOR issues with docker databases over cifs or nfs) and an awesome docker image for volume backups: offen docker-volume-backup It stops the desired containers before a backup, creates a tarball, sends it to an S3 bucket on my truenas server, spins up the stopped containers and lastly a cloud sync task on my truenas encrypts the data before pushing the backup to the cloud.

[@christianlempa]

Glad it was helpful!

[@christianlempa]

What were the issues with the DBs?

[@huboz0r]

Btw, one point i need to add here: why share all of your files as root? You could just make a new group and user(s), specifically for accessing your files, and map your NFS shares to them. It is belt and suspenders since you only expose NFS to a specific IP, however not using root whenever possible is the way forwards. Probably why it got removed as a default in the new release.

[@christianlempa]

Yep that’s something I need to get fixed in the future

[@Muhammad_Hannan9914]

I read somewhere the NFS is not secure when used with container as it also open access to container processes to get into the main OS processes when we expose server file system to docker container. What's your thoughts on this? Any one.

[@markobrkusanin4745]

Gluster FS will be even better option to manage data inside Docker swarm.

[@christianlempa]

I'm so interested in these filesystems, once I finish my projects I start looking at them

[@wuggyfoot]

wow dude when you typed root in that box you solved all of my problems crazy how ur the best source of information i have found over all of the internet

[@Grand_Alchemist]

Event with the "wheel" user added to TrueNAS, NFS refused to work for deluge /sonarr / radarr (CentOS using docker compose). I ended up making an SMB share (yes, Microsoft, blasphemy!) and it works perfectly. So much less of a headache than NFS, PLUS it's actually secure (authenticated with a password and ACL (Access Control). SO, yeah. Unexpected but I would just recommend making a fricking SMB share.

[@desibanjankri5646]

LOL I spent a week on figuring this exact thing out - wanted to use Photoprism to use pictures from Backup server rather than Import files into Docker. Just got it working last night.😂

[@christianlempa]

Haha great :D

[@yangbrandon301]

Thank you. A great tutorial for NFS.

[@nixxblikka]

Nice video, looking forward to true nas content!

[@christianlempa]

Thanks! 😀

[@reppich1]

you are so deep in the weeds here, not accessible to people who are still finding their way... the level this is at is for people who don't actually need this.

[@Telmosampaio]

I usually do a cron job to copy volumes and database exports to an AWS S3, and then another cron job to delete files older than 1 month!

[@Sama_09]

once installing nfs-common things just worked !! nfs-common was the missing piece

[@kanarie93]

isnt it better to map the NFS volume in a /mnt/NFS on the host running docker so you have 1 connection open instead of hunderds for every container picking its own connection? Or is that not possible when you go docker swarm?

[@KilSwitch0]

I have this exact question. This is the way unraid handles this. I think I will duplicate UnRaids approach.

[@tuttocrafting]

I have a docker user and group on both docker and Nas machines. I use the same UID and guid on the container using env variables.

[@Dyllon2012]

For databases, I feel you'd be better off just taking backups and keeping a read replica or two. You'll almost certainly get better performance plus you'll be able to recover faster with the replica. If your app isn't a database, it should probably not be saving important data directly to disk unless you're doing some ad hoc operation (like running tests) where a local volume is fine. The NAS is probably more convenient for transferring files, I'll give it that.

[@christianlempa]

I hear that a couple of times, but never found any resources or details why this should be the case. Could you kindly share some insights? Thanks

[@streambarhoum4464]

Christian, How to make a disaster recovery of the entire system ? could you simulate an example?

[@StephenJames2027]

7:48 After many hours I finally figured out that I needed NFS4 enabled on TrueNAS to get this to work on my setup. I kept getting Error 500 from Portainer when attempting this with the default NFS / NFS3. 😅

[@christianlempa]

I’m glad the video helped you :)

[@myeniad]

Great explanation. Thanks!

[@christianlempa]

Thank you 😊

[@Got99Cookies]

Wouldn’t raidz2 be more safe especially with a 12 drive arrays? Good video tho! Docker volume management is something very important and you made some very good points!

[@christianlempa]

Yea, it would be. You can possibly argue if that would be a better option, I still think it's unlikely that more than 1 hard drive fail at the same time, but hey... people might have seen this in the wild, undoubtedly. That's why offsite backups are important.

[@devinbuhl]

You would be surprised at how easy it is for another drive to die while your pool is resilvering from a 1 disk failure.

[@FunctionGermany]

Don't you need higher-tier networking to make sure you're not suffering any performance penalties? I can imagine that the additional latencies can make certain applications run slower when all file system access has to go through 2 network stacks and the network itself.

[@charlescc1000]

I have been running some basic selfhosted containers on my servers in a similar configuration as laid out in this video. (Ubuntu server with portainer & Docker connected to TrueNAS for the storage.). My TrueNAS is setup with mirrored pairs instead of raidz/raidz2- but it’s still over a 1Gbe LAN. It’s been fine. Yes I’m sure 10GbE would improve it, but it’s plenty usable for most containers. I originally set it up as a test environment before buying 10Gbe hardware and then it worked so well that I decided not to bother with 10Gbe (yet) It’s not great with a VM that has a desktop environment- but it’s been fine with server VMs. Not fantastic, but fine.

[@christianlempa]

Thanks for your experience! I'm running it with a 10Gbe connection, but I highly doubt this would make a huge difference in this case. As for VM-Disks this might be totally different, of course, but for Docker Volumes 1Gbe should be fine.

[@ElliotWeishaar]

You are correct. The approach outlined in the video is great! And I would recommend this approach to pretty much anyone starting with docker. As you continue your journey you will have to adapt to the requirements of what you're hosting. You are correct in saying that some applications don't play well with storage over the network. Plex is a big one. I tried hosting my plex library (the metadata, not the media) on NFS, and the performance was atrocious. The application was unusable, and I had to switch to storing the data locally. I suspect it has to do with SQLite performing tons of IOps which NFS couldn't handle. This was with a dedicated point to point 10GBe connection as well. I was using bind mounts instead of docker volumes but I don't think that created the issue (could be wrong). I have other applications that have experienced this as well. I've resorted to having all of my data be local on the machine, and then just create backups using autorestic.

[@nevoyu]

Your not serving hundred of connections at a time. So really your not needing as much performance as your think. I run a 1gb connection to my homelab with a 4 disk raid 10 array and I can't tap the full bandwidth of the connection but I have no issues with performance watching 1080p (since I don't have a si gle display 4k makes sense on)

[@robmcneill3641]

@@ElliotWeishaar I ran into the same issues with Plex. I did end up storing the media remotely but could never get the library data to work reliably.

[@Steve3dot1416]

Some dockers don't like shares. Those who use SQLite as a database for example. I had big performance issues with Lidarr who was caused by database lock issues because SQLite does not work well when in a share. I understood this has something to do with file links. I had to fall back to local volumes because of this.

[@macenkajan]

Hi Christian, great Videos. I would love to see how to use this NFS (or maybe iSCSI) Setup with a Kibernetes Cluster. This is what I am trying to setup right now ;-)

[@christianlempa]

Thanks mate! Great suggestion, maybe I'll do that in the future.

[@ViktorKrejcir]

Next level: Longhorn :)

[@christianlempa]

😁

[@Billyfelicianojp]

I am having issues installing a stack in a Volume. the volume is already added in portainer and I see it and Tested it but my yml I cant figure out how to add nextcloud to the volume I want it.

[@Dough296]

What if you need to perform an update on TrueNas that needs to reboot the NFS service or the TrueNas system ? Will the Docker container wait for the NFS service to come back without having trouble with data consistency ? I have myself that setup but when I want to restard my NAS it's a real pain to stop everything that depends on it...

[@zaberchann]

One concern of using NFS in a home lab is that NFS needs the user to ensure the local network is safe, otherwise the security is compromised since the only auth is the ip address (of course you can use kerberos, but it’s too hard to configure). Besides, an malicious docker container could connect the NFS by using the host ip.

[@christianlempa]

Fair point!

[@alexanderbradley5009]

Rook Ceph could also be an alternative to NFS

[@christianlempa]

I'm so interested in these filesystems, once I finish my projects I start looking at them

[@macpclinux1]

if i ever go crazy and have to setup a dirty docker system i'll try to remember this. it seems really helpful and imo any improvement possible is a god's gift with docker (i really hate it, ngl kubernetes. also not a big fan)

[@gonzaloamadorhernandez7020]

Oh my gosh!!! You are a crack !!! Thank you very much, mater

[@christianlempa]

Thanks 😆

[@yotuberrable]

In this case I assume NAS server must always be started before docker server and shutdown in reverse order. Otherwise I assume containers will just fail to start. How do you guys handle this?

[@MarkJay]

I also would like to know how to handle this.

[@MarkJay]

What happens when you need to reboot or shutoff the storage server. Can the docker containers stay running or do they need to be stopped first?

[@nevoyu]

You don't need a "NAS operating system" any operating system can act as a nas as long as it supports some firm of network file share (ssh, nfs, smb, isccsi, ect)

[@christianlempa]

That's what I said in the video ;)

[@RobbyPedrica]

Great video.

[@christianlempa]

Thanks!

[@Spydaw]

Awesome video, thank you for explaining this. I am doing the exact same with all my pods in k3s ;)

[@christianlempa]

Oh, that is cool! I'm planning that as well in my k3s cluster I'm currently building ;)

[@Spydaw]

@@christianlempa Feel free to ping me if you have any questions ;)

[@vidiokupret]

Thank you, it really helps

[@christianlempa]

Glad to hear that!

[@black87c4]

NFS stands for "Not For Servers" ;-) Sys admin for about 30 years now, always cringed when i got a request for NFS on any app. For home use i'd be ok with it tho

[@dragonsage6909]

What would you suggest for a production system instead!?

[@samuelbrohaugh9539]

Great question, please tell us what you recommend instead

[@dragonsage6909]

@@samuelbrohaugh9539 I'm asking you because I'm using NFS.. not being sarcastic, trying to learn the most secure best method.. if you know one.. thanks in advance! :)

[@black87c4]

@@dragonsage6909 Using a cluster filesystem is typically much better but I understand doing clusters is typically not cheap either. Guess it depends on what your talking about app wise. Is it a high avail app where downtime costs money or something simple that can handle user downtime. NFS will fail at some point, mount becomes stale, network issues locking up apps, etc. Its simple to implement, easy to use but easy to fail. Home use rarely an issue, real production use make sure expectations are met and understood. Just experience talking.

[@dragonsage6909]

@@black87c4 awesome answer, thank you. I'm looking at some other options now, think I've got it.. will update asap

[@AJMandourah]

I have read around some people complaining of database corruption using NFS as their cluster storage, didin't tried it personally and I am currently using CIFS mounts for my docker swarm. I was wondering if you have tried Glusterfs as it seems it is recommended for cluster volumes in general ,

[@christianlempa]

I hear that a couple of times, but never found any resources or details why this should be the case. Could you kindly share some insights? Thanks

[@Felixls]

Yeah, well, any application using a sqlite database will get corrupted sooner or later using a volume from a network share. I've lost so many hours and tried so many different solutions, like CIFS, NFS, GlusterFS, you name it, it doesn't work, and it never will. The only solution is to use a local directory or a docker volume (which is local).

[@pedro_8240]

And how do I use NFS to mount the initial portainer data volume, before configuring portainer?

[@HelloHelloXD]

Great topic. One question. What is going to happen to the docker container if the connection between the NFS server and docker server is lost?

[@christianlempa]

The container will fail to start

[@HelloHelloXD]

@@christianlempa what if the container was already running and the connection was lost?

[@vladduh3164]

@@HelloHelloXD it seems that the container just keeps running, it may not be able to do anything tho, i just tested this with sonarr as i had the /config folder in the nfs volume and it seemed to work as long as it didnt need anything from that folder, when i clicked on each series it just showed me a loading screen until i reconnected it, I suppose the answer is it depends entirely on what folders you put in that volume and how gracefully the application handles losing access to those files

[@HelloHelloXD]

@@vladduh3164 thank you.

[@MadMike78]

Love your videos. Question how would I use portainer to add new volume to existing container? I found how to add the volume but after that I don't know if anything needs to be copied over.

[@GundamExia88]

Great Video! I have a question, so , if I have mounted the volume to the NFS in /etc/fstab. Do I still need to create the nfs volume? couldn't I just point to the mounted NFS on the host? What's the advantage of creating a new nfs volume in portainer? Is it just for easier to migrate from nfs to nfs? Thx!

[@christianlempa]

It's just for easier management. If you already have NFS mounted on the host, that is totally fine

[@mydogsbutler]

Have to disagree with the thesis that its' better to have db on remote server. It doesn't follow the 3,2,1 strategy for backups. From a disaster recovery standpoint you are better off having two copies rather than 1. It's also slower as data has to make a roundtrip to remote server rather than local. That said it might have a use case for local lab or test server (e.g. remote share could be zfs whereas docker instance could be on cheap single drive minipc partitioned with ext)

[@leokeuken9425]

You could just simply push your builds to a remote server running a private docker registry and have that server run daily backups. Out the box docker on overlay2 doesn't like nfs *at all*. Better off using the cache to and cache from flags on buildkit if you are looking for any advantages of sharing layers across multiple machines provided you do have the cache target mounted on a shared fs. And even with that the time it costs to import and export to cache puts question marks on the absolute performance gains for builds.

[@R055LE.1]

One correction here, NFS v4 does use authentication, and you should be using that much more secure method instead.

[@christianlempa]

Thanks for sharing!

[@scockman]

Another AWESOME video!! But, I saw in the video that you have a portainer_data volume on the nfs share, how was that done? I have been trying to get this to work but getting docker error while trying to mount the volume.

[@christianlempa]

Thanks! You need to do it outside of the gui with docker cli commands unfortunately.

[@gjermundification]

I run my local storage lofs across several zpools. Not sure why anyone would do anything as complicated as docker when there are open solaris zones on zfs. In essence I run the server application part on a zpool that is in RAM and NVMe, and storage in RAM and spinning drives. ZIL, L2ARC, and all... I use NFS between the Mac and the media servers.

[@christianlempa]

There are a couple of reasons why Docker is useful ;)

[@rw-xf4cb]

Could use iscsi targets perhaps worked well with VMWARE esx years ago when i didnt have a san

[@manutech156]

Any plans to do a tutorial for Kubernetes Persistent Volume to TrueNAS NFS ?

[@KR1ML0N]

i use all my docker volumes via nfs. It works pretty well.

[@christianlempa]

Thanks for sharing! It also works great for me ;)

[@oakfig]

Are you from the home of Arnold Schwarzenegger? You have his accent. Can we hear you say, " put the cookie down, now!" 😂

[@christianlempa]

Lol no, Arnold originally comes from austria, that's not quite Germany 🤣

[@YordaNii]

There is another way too , make shared nfs folder , mount it to your vm , and then just bind it directly there.

[@christianlempa]

Thanks for sharing!

[@RileySalm]

I did this a few days ago and it corrupted several of my containers. Please be carful and have backups if you do this.

[@esra_erimez]

Would you please do a video about using Ceph Docker RBD volume plugin?

[@christianlempa]

Hmmm I need to look that up, sounds interesting

[@RiffyDevine]

The folder/volume I created inside the container is user 568 so I can't access the /nfs folder in my container. Why did it use that user id over root?

[@area51xi]

When I try to deploy I keep getting a "Request failed with status code 500." error message.

[@anthonycoppet8788]

Hi . Created nfs volume on server. Can connect with the synology. But in portainer. The nfs volume appears empty .. The server volume is nobody;nogroup.

[@maxime_vhw]

The nfs share mounts fine to my test ubuntu container. But i cant access it. Permissions issue

[@tl1897]

I tried this some time ago. Sadly my pi4 with 3 HDD's in raid5, using mdadm was not fast enough. So i decided to have my deployment files on the nfs, but volumes locally. And i wrote backup scripts for the rest.

[@GSGWillSmith]

I don't think this is working anymore. It used to work, but now on TrueNAs 13, I keep getting this error with new volumes I create (both via stack editor and in portainer): failed to copy file info for /var/lib/docker/volumes/watchyourlan_wyl-data/_data: failed to chown /var/lib/docker/volumes/watchyourlan_wyl-data/_data: lchown /var/lib/docker/volumes/watchyourlan_wyl-data/_data: invalid argument

[@gunnsheridan2162]

Hi Christian, thanks for the informative video. I have two questions though: 1. What is the correct way of setting user with same id, group id on nfs server and client? I have rpi with user 1000:1000. Such user doesnt exist on my Synology. Should I add new user to synology? Or should I pick one of synology user ids and create such user on raspi? If so, how do you create user with specific ids? 2. What about file locking through nfs? I had issues with network stored (samba cifs) data containing sqlite database, for example homeassistant, baikal. I couldnt network store mariadb, mysql either due to some "file locking issues".

[@vmdcortes]

Awesome!! Is this a good solution for a docker swarm volume sharing with the different nodes?

[@christianlempa]

Thx! I'm not sure about that, I think NFS is still the easiest for my setup.

[@devinbuhl]

Couple misleading things in this video. 1. Snapshots and RAID are not a back up. 2. Not all workloads can use a network file share for its persistent data. Anything that relies on file locking is best put on block storage, that includes postgres and sqlite w/ WAL databases. If you choose to use NFS for these you are risking data corruption. It's important to know the difference between file, object and block storage and when to use each one. Educate yourselves!

[@ebeltran]

Any recommended videos on the subject?

[@christianlempa]

Thanks for giving me another video topic :)

[@D76-de]

First of all, I don't have much knowledge about Infrastructure... T,T Can the NFS of truenas VM be delivered to a container volume without 1Gb Network bottlenecks? Both truenas and container (ubuntu VM) are operated on proxmox.

[@226cenk9]

This is nice, but. Is there a way to use a local directory on the host instead? I have docker installed on my Ubuntu 22.04 and it would be nice to use local directories.

[@crckdns]

Not running docker because I couldn't manage to run one single "package" on my qnap in station container (had some network problems).. That's why I'm using native running installations all the way without some voodoo in a package.

[@adamskalik3458]

It does not work for synology, it creates volume on for example @docker folder which is not visible for standard user

[@Weirlive]

with synology I had to build the volumes in the CLI of the host.. doing it in Portainer doesn’t seem to work for me.

[@ettoreatalan8303]

On my NAS, CIFS is enabled for the Windows computers connected to it. NFS is disabled. Is there any reason not to use CIFS instead of NFS for storing Docker volumes on my NAS?

[@Ogorodovd]

@christianlempa Thanks Christian! Could install portainer on a Debian VM within TrueNAS scale, and then communicate with that? Or are you using a separate machine entirely for your Portainer/Server?

[@christianlempa]

I think that should also work

[@mistakek]

Do you stop your containers when you backup your storage server?

[@jp_baril]

Good question. Because the video stated that backuping the local volume directory was not ideal for databases, yet it was never explained if doing snapshots on the nfs server was overcoming those mentioned potential issues.

[@mistakek]

@@jp_baril Exactly why I asked.

[@christianlempa]

Great question! It depends on the storage server's file system and how you do the backup. If the Backup Server would just "copy" the files away, then the container should be stopped. If you're using ZFS with a snapshot, it shouldn't be a problem. I haven't had any scenario where this would result in an inconsistency issue with the db. However, if you do a rollback, you should of course stop the container, restore the snapshot and then start the container again.

[@mistakek]

@@christianlempa Now I think I should have my TrueNas as my main nas, instead of my Synology.

[@solverz4078]

What about storing portainers volumes on a NFS share too?

[@andrewcrook6444]

Synology removed nfsidmap as far as I can see so can’t do user mapping. They are pushing Kerberos for authentication, identity and mapping.

[@rallisf1]

This is just bad advice. 1) Most databases won't work well over NFS due to lacking file locks, if you need real time db sync setup a cluster 2) Keeping all your files in a single system gives zero redundancy, doesn't matter if it's a worker node, a storage node or a NAS. You can always setup raid/zfs/truenas on your worker node (main docker server), in fact truenas has a docker interface of its own (although lacking compared to portainer), but you will only achieve redundancy by syncing data with another system (thus having the same data in 2 or more systems). 3) RAID is not a backup, always take proper backups. Ideally use something like borg/restic/duplicati to handle them

[@christianlempa]

Thanks for your comment, however I disagree with you saying it was a nad advice. However I'd like to find out more about the NFS DB problem, you find barely valid info on this topic. Most comments are 10 years old and just saying "don't use nfs with dbs". But since the introduction of file locking support in NFSv4 and further improvements in v4.1 as we're using it in this video, I'm kinda questioning if that is still a serious problem. If you have more info about it, please share, I'm really interested in. The whole discussion with redundancy, backup and raid was never a topic of this video. I might cover this in a future video, because you’re totally right. You need a proper backup strategy!

[@TheManuforest]

Hello guys ,... I had a power failure and all my docker volumes have gone. Is this a predictable behavior ? Are they still there in disk ? Thanks

[@j4nch]

I'm far from an expert on linux and there is something I'm missing on permissions: When you say that we need to have the same user that use the same permissions between the NFS server and the docker image, how does it work? I though that just having the same user id or the same user name isn't enough, no? I mean, they could have different password ? Also, what about the performance implications? I'm thinking to move my plex server in a docker container, with its storage on a NFS volume, could this be an issue?

[@SebastianSchuhmann]

Did you experience problems with containers using NFS mounts after a reboot? Until now I used nfs only via mounting it to the host and bind mounting docker volumes to the host Since I now switched to the "direct mount" of nfs to docker host, specified in the stack code, after rebooting my CoreOS server, all these containers fail After restarting them they start fine Seems like a not available nfs service at boot time where the containers try to start but are not able to be mounted yet

[@christianlempa]

I mostly reboot both of my servers, so the NAS server and the Proxmox Server, then it works fine.

[@xD3adp0olx]

Is it possible with samba/cifs as well?

[@Photograaf11]

Hi! Would it also be possible to do something similar for the "stacks" that are created with portainer??? Or maybe this is stupid... images are not downloaded over and over again when there is an update for example (like a local cache system). Great video, as usual!

[@christianlempa]

Thanks! I guess that's working as well, but I haven't looked into compose yet

[@martinzipfel7843]

I'm trying to do this for hours now and always run into permission issues. My User on the docker host and the NAS are exactly the same (same username, pw, UID GID) and I get permission denied when I just try to cd into the NAS folder from the ubuntu test container. Anyone an idea?

[@mrk131324]

How about volumes where performance matters? Like tmp or cache folders or source files in local development?

[@christianlempa]

You can still use local volumes in that case

[@rodrigocsouza8619]

@christianlempa is the activation of NFS4 that simple?? I've tried exactly what you deed and the mount fails returning "permission denied", always. I tried to dig on the subject and looks like that NFS4 requires a lot of effort to get working.

[@Invaderjason123]

no matter what I do, I can't get the volume to mount.

[@kevinhilton8683]

Hmm seems based on the comments iscsi might be the way to go which is block storage vs nfs which is file storage. I don't know however but I do know when I've had two linux system sharing via nfs the nfs connection has crapped out in the past causing problems. I'm not sure this is a better option than keeping bind mounted volumes and just having a backup solution for the volumes that runs periodically to backup the volumes to remote source. Lastly I'm wondering if you run an ldap server since this would synchronize users on vms and the NAS. I'm curious if you would get nfs errors in this scenario

[@christianlempa]

Currently I don't have LDAP, but I'm planning setting up an AD at home