Haven't been following the macOS updates closely but a big feature I'm looking forward to in macOS 26 is Apple's container solution as an alternative to Docker.

The "container" command line tool: https://github.com/apple/container

The underlying Containerization package: https://github.com/apple/containerization

The main improvement over Docker on Mac is that it uses separate lightweight VMs per container, instead of one shared Linux VM hosting all containers. This means the RAM allocation can be dynamic instead of the user having to decide how many total GB to allocate for the Docker VM. So if I'm running a lot of containers I expect it to work without manually changing settings, and if I'm running only a single container then I expect it won't waste resources with allocated-but-unused RAM.

Currently these repos are on version 0.4.1 and 0.8.1 respectively, which tells me they're not ready yet. Hoping they're ready around the time macOS 26 releases to GA.

so I have a setup where I have a NUC that has docker on it, one of the containers is my nextcloud that I use for sharing my files across my computers.

I also have a synology NAS which is connected to my NUC via NFS and the files themselves are stored on that NFS file via a docker volume mount.

Hopefully that made sense.

My problem: not often but it does happen where my router has an issue, today it just needed a restart. another time it was cause I deliberately disconnected it from the power not realizing it would mess up the connection between my NUC and my NAS.
Why is this an issue? it causes my nextcloud to freeze up as the files it is supposed to share are no longer available. necessitates me restarting my NUC to get the connection going again.
Thankfully hasn't happened often but still something that can be scary in the moment. My question is, is this just one of the pitfalls I have to accept of utilizing a NAS the way I am or is there a way to connect a Synology to a NUC and ensure router issues don't cause the nextcloud docker instance to freeze?