@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)
Graham Sutherland / Polynomial's Post
In Reply To: this post
Likes: 0
Boosts: 0
Hashtags:
Mentions:
@snep@y.diskcat.com
@dragonarchitect@rubber.social
Comments
Displaying 0 of 1 comments
Snep :floofHappy:
In response to this post@gsuberland @dragonarchitect It really just sounds like a bad implementation in this case that disallows proper customization in the GUI of installed containers. I've never done any work with any CI/CD or IaaS implemenations and I still think Docker is great for single instance applications /because/ the containers can reliably be set up in a repeatable way on any machine the engine runs on, /because/ they are immutable outside of mount points and env variables. Less friction than DIYing it IMO
@snep @dragonarchitect so one example of a major friction point here is when things have bugs. a while back I had installed a popular webapp thing in a jail. they also publish it via docker. there was a bug that affected my install. I reported it and sent a PR but it didn't get fixed in a release for 9 months.
on CORE: `iocage console thething; nano /path/to/broken.file` and patch it
on SCALE: haha hope you like maintaining and publishing your own dockerfiles (also you don't get updates now)
by Graham Sutherland / Polynomial ;
Mentions: @gsuberland@chaos.social @dragonarchitect@rubber.social
Likes: 0
Replies: 1
Boosts: 0