Virtual Machines let us abstract away our hardware resources. They also made deploying new instances much easier than it was previously, so we started using more instances than we would ahve without it, just to provide configuration and resource separation.
The first part is still necessary - and we still need multiple instances to take advantage of multiple VM hosts when it comes to scaling and redundancy. The second part is what containers address.
I have a feeling we will end up mixing and matching the two as appropriate.
Containers are - depending somewhat on the container technology used - from a user perspective just like a VM that happens to be restricted to running the same kernel as the host and use less resources. Some container systems may leak more in terms of abstractions and/or might not be designed to be as secure, and so there's certainly scenarios where certain types of containers are not appropriate, but that's an issue of specific implementations.
In the systems I deploy, containers takes care of all of what you describe all by themselves.
That's only true when the OS's in question require different kernels. For OpenVz/Virtuozzo for example their RHEL based kernel has long been the preferred one for a lot of people for non-Redhat Linux versions too.
I agree with you there are still lots of reasons people will want VM's though.
We've picked containers at work, but only because while we host customer sites, we run and manage all of them, and so have a lot of flexibility a typical hosting provider doesn't have.