@gsuberland @dragonarchitect But isn't that the core idea of Docker anyways? It is weird you can't set up an internal Docker network and have services be forced to use the Host network mode, but being unable to make persistent chages to files inside a Docker container that aren't mounted in from the outside without creating a custom Dockerfile and thus a custom Docker container based on another one is what Docker is all about after all 🤔
Snep :floofHappy:'s Post
In Reply To: this post
Likes: 0
Boosts: 0
Hashtags:
Mentions:
@gsuberland@chaos.social
@dragonarchitect@rubber.social
Comments
Displaying 0 of 1 comments
Graham Sutherland / Polynomial
In response to this post@snep @dragonarchitect yes and it's shit for this kind of use case
@snep @dragonarchitect like that's all well and good if you're an enterprise building infrastructure-as-code stuff with build artifacts and CI/CD and all that cargo cult shit, but for a NAS it's super high friction and very annoying (especially because it has no UI for compose - if you want anything beyond the container as-is plus some mounts you're generally SOL via the UI)
by Graham Sutherland / Polynomial ;
@gsuberland @dragonarchitect I wonder, what use case do you mean exactly? Installing extra server apps onto a NAS OS? Because I feel like a (proper!) Docker implementation is perfect for that, compared to LXC containers or VMs for example
by Snep :floofHappy: ;
Mentions: @snep@y.diskcat.com @dragonarchitect@rubber.social
Likes: 0
Replies: 2
Boosts: 0