We used it for some testing environments, and Docker largely removed the need for it for us as well. A simple docker-compose file is often far quicker to start and with much less local system overhead than the typical VM vagrant might spit out. It’s also much more reliable - if “docker-compose up” passes for me, it’s very unlikely to fail for others. Vagrant has much more external dependencies (things like virtualbox etc) and often users can have differing versions that introduce all kinds of fun issues.

Personally I now just put a little effort into shoving whatever software we might need into a container, it’s usually not that difficult for web app style stacks.

I am by no means arguing docker plus docker-compose is a 1:1 replacement for vagrant, but for many use cases I think it can be much nicer. I would only resort to vagrant in the event containers cant solve the task at hand now.