How “It works in my machine” turns to “It works in my container”

Re:How “It works in my machine” turns to “It works in my con... by verdverm on Friday July 28, 2023 @11:38AM (#36908478)

You seem not to have worked with the VM tools that do the same thing as a Dockerfile. Had you, you would realize that your points are invalid and I can have the same guarantees with VM as containers

If you think Dockerfiles are great, then you haven't hit the day 2 problems yet or explored the better alternatives for defining containers.

Also, the whole point of the original post is to point out that what you are saying is not magically true for containers

[ Parent | on HN ]

Re:How “It works in my machine” turns to “It works in my con... by jchw on Saturday July 29, 2023 @10:49AM (#36920836)

That's exactly what I have been saying, though. Prior to Docker, there was nothing like Dockerfiles or OCI images. The closest thing I can think of was Vagrant, but it's missing a lot of what makes Docker good.

The reason why containers are good is entirely about the concepts, NOT the actual engine or technologies. Again, you can literally run OCI images in a virtual machine; Ignite will run them in a KVM. That's as literal as you can get.

Docker existed and did a lot of the same things it does today in 2013.

[ Parent | on HN ]

Re:How “It works in my machine” turns to “It works in my con... by verdverm on Monday July 31, 2023 @11:47AM (#36944419)

FreBSD jails predate containers, same idea. https://en.wikipedia.org/wiki/FreeBSD_jail

The ONLY thing docker did was make a small amount of questionable UX around the low-level container primitives. They did not invent anything, definitely not containers. I could share VM images before Docker, nothing new there... the concepts all existed before containers.

You can literally run... anything... on a VM, why make a point about being able to run OCI images? This is like a no-op.

[ Parent | on HN ]