@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)
Comments
Displaying 0 of 1 comments
Snep :floofHappy:
In response to this post@gsuberland Yeahh, that definitely is annoying whenever it happens. I'm surprised the bug remained for this long, but some devs teams are like that, I s'pose.
Though, at least with regular Docker, you should still be able to get updates even when you've built a patched Dockerfile ontop of another container. If you specify to always use the latest version of a container as a base, your changes will be applied on top of the most up-to-date version with each rebuild you kick off.
@snep which would break on update, no doubt
by Graham Sutherland / Polynomial ;
Mentions: @gsuberland@chaos.social
Likes: 0
Replies: 1
Boosts: 0