> well, each and every single one of them has to be maintained, updated for security fixes...
Then you patch it by redeploying it.
> Not to mention the likely possibility of breaking API changes in the container version. vagrant/puppet I'm looking at you, nothing is worse than having to figure out which ancient version of vagrant and puppet was used at creation in order to get the system running again
Is this a real issue that people run into? I've never had any issues with this.
> Or, well, look five years in the future, and hope today's hyped container solution will still be present then.
Good thing the real work essentially boils down to some scripts which can be easily translated into any new technology
> Fuck containers, get a properly managed ordinary Debian server and save yourself a lot of headaches.
Then you patch it by redeploying it.
> Not to mention the likely possibility of breaking API changes in the container version. vagrant/puppet I'm looking at you, nothing is worse than having to figure out which ancient version of vagrant and puppet was used at creation in order to get the system running again
Is this a real issue that people run into? I've never had any issues with this.
> Or, well, look five years in the future, and hope today's hyped container solution will still be present then.
Good thing the real work essentially boils down to some scripts which can be easily translated into any new technology
> Fuck containers, get a properly managed ordinary Debian server and save yourself a lot of headaches.
Spotted the Debian sys admin!