It's fucking bullshit if you don't have local storage though. You can't just mount the docker directories to an NFS folder, they require features that are unsupported by nfs. If you want to use network storage you have to mount a loopback file, it sucks.
PVRE schizophrenia
https://docs.docker.com/reference/cli/docker/volume/create/ mentions specifically creating a volume on NFS. Maybe it doesn't work when it's a bind mount?
No, I'm talking about storing the containers and/or their build artifacts themselves. Not data for containers. I have really cheap shitty boot SSDs in my good 14700f "server" because I have a massive fuck off NAS to actually store data, and when I've had to compile modified versions of containers for particularly large projects containing cuda/pytorch etc not only do I get fucking I/O limited with local storage, obviously it *runs out* when I keep changing broken shit and retrying the compilation, and this shit takes hours to compile so wiping out the cache completely isn't desirable either. I hate docker so much!
Oh right. Yes, I think it needs to be either overlay2 or btrfs.
Or loopback mounting /var/lib/docker as a block file on the NAS over the network, which is the most sane option. I can't use an NVME. All the PCIE is taken. I put all my expensive storage in my NAS FOR A REASON! Maybe docker should be LESS SHIT and work with CONVENTIONAL STORAGE SYSTEMS.
Interesting that he chose Linux for Niggers, but I suppose that's where all normies start out, including me.
Ubuntu is good, unironically. I wouldn't use the stock UI and would opt for XFCE personally but as a distro it's very straightforward, just works, and everything works with it.
True, for the average person its a "just works" distro, and the desktop environment flavors are cozy. Though I haven't used it since around the time Snaps first got introduced so I can't say much about how good it is now.
My first Linux distro was Red Hat 6.
I may be mistaken but isn't running code over the network a bad thing? Like any latency or dropped packages can cause the containers to error or crash?
Directly attached storage has latency and r/w errors too my guy. There are billions and billions of docker swarms that are operating out of network storage right now, they just aren't directly mounting an nfs share to /var/lib/docker (since that is impossible). Core operating sytems are netbooted (PXE) all the time... It's taken into account.
I may be mistaken but don't those docker storms precache the container images? Like there's a repository where the images are stored, and when a specific unit goes to deploy an image it downloads a copy of it to local storage before starting it?
He has started to hate modern tech like Rossman does. His older videos give it away.
It depends. It doesn't have to be docker either. Diskless servers are a thing.
The guy who has to hire a dude to like, change his fucking spark plugs on his car channel can't do anything but MacOS?
Diskless servers load the os and programs into a ramdisk, or offload processing to a different server that has the applications installed locally. nobody is trying to run an application directly off a network drive, and any relevant guide where the topic comes up says not to do it.
