4 ms·
* learning curve of new technology: you need a new set of tools, you can't just use free/ps/top/etc. (well, you can use them, but you don't get as much insight
by oblio 9y ago
* learning curve of new technology: you need a new set of tools, you can't just use free/ps/top/etc. (well, you can use them, but you don't get as much insight as you get by using the container tools directly); you have to learn yourself, you have to train colleagues and newcomers, etc.
* increased complexity if you have a simple setup; for example if your deployment now consists of copying just 1 file or 1 folder and starting up an app/service, then using containers will include additional moving parts in your setup
* if you already have legacy tech, migrating won't be straighforward, especially for stateful applications (think JSF, ASP.NET Forms, etc.)
* as jeremyjh pointed out below, unless you have a specific strategy for this, you will have duplicated dependencies in containers, which need to be checked for vulnerabilities; you can't just apt update && apt upgrade on the host system from just the security repositories and call it a day (more or less)
* an extra layer that comes with its own bugs