The sad state of sysadmin in the age of containers (2015)
1–10 of 324 posts
Re: The sad state of sysadmin in the age of containers (2015)
#2I don't know that much about the state of container systems these days, but to me it seems it's the "comfortable" way in the "security vs comfort" tradeoff. Use where applicable and hope for better days.
Re: The sad state of sysadmin in the age of containers (2015)
#3Discussed at the time (443 comments): https://news.ycombinator.com/item?id=9419188
And again in 2018 (426 comments): https://news.ycombinator.com/item?id=17083436
Re: The sad state of sysadmin in the age of containers (2015)
#4ha +1 for the build tool mess. its like everyone goes "duuude this stuff is so complex lets build something on top to abstract it all away" and you end up with another level of complex stuff that builds the stuff that builds the that wraps the stuff that you originally wanted to use...
Re: The sad state of sysadmin in the age of containers (2015)
#5Discussed at the time (443 comments): https://news.ycombinator.com/item?id=9419188 And again in 2018 (426 comments): https://news.ycombinator.com/item?id=17083436
But unfortunately, it's relevant to this day.
Re: The sad state of sysadmin in the age of containers (2015)
#6Terrible article IMO. Hadoop is an awful mess, but it has nothing to do with Docker, which is simplistic in comparison.
"Ever tried to security update a container?"
Yes, I have! In fact you can maintain patch compliance in a container pretty much the same way you'd maintain a VM or bare metal Linux installation!
Re: The sad state of sysadmin in the age of containers (2015)
#7Re: The sad state of sysadmin in the age of containers (2015)
#8I don't know that much about the state of container systems these days, but to me it seems it's the "comfortable" way in the "security vs comfort" tradeoff. Use where applicable and hope for better days.
But there are some environments where security is (almost) the only relevant factor, e.g. banking IT-infrastructure. I don't want my bank to pull arbitrary images from Dockerhub because that increases their comfort.
Conversely, if I were sysadmin at a bank I would most definitely be concerned what was running in my network.
Re: The sad state of sysadmin in the age of containers (2015)
#9I don't know that much about the state of container systems these days, but to me it seems it's the "comfortable" way in the "security vs comfort" tradeoff. Use where applicable and hope for better days.
I don't think you should put security at any case in tradeoff, by your argument one can save passwords in plaintext because its easy and comfortable, but its just not acceptable and this would effect not only your app but every app that your users use.
Re: The sad state of sysadmin in the age of containers (2015)
#10I don't know that much about the state of container systems these days, but to me it seems it's the "comfortable" way in the "security vs comfort" tradeoff. Use where applicable and hope for better days.
I don't think you should put security at any case in tradeoff, by your argument one can save passwords in plaintext because its easy and comfortable, but its just not acceptable and this would effect not only your app but every app that your users use.
I see the value when running e.g. home instrastructure on some old laptops or other non-critical stuff. Most people have NAT at home and thus whatever services they pull and listen in their local network aren't exposed to the outside world, and they can enjoy mopidy/NextCloud/whatever without going through a lot of hassle setting it up.
Of course once we come to enterprise environments the opaque build/deployment process is atrocious.