41–44 of 44 posts
I was interested in how they got containerization working on a kernel which to my knowledge lacks the required primitives. What I found was marketing looking to treat containerization as nothing more than a buzz word. The article is tone deaf. It talks about running foreign OSes and legacy support proud in itself because docker cannot. Yet blind to the reason docker cannot: Docker is containers! Any VM can do what th…
Yeah, this page[1] outright admits that it is virtualization, not containerization. I'd rather wait for the next version of Windows which will have true built in containerization and will work with Docker [1] https://spoon.net/docs/getting-started/transitioning-from-do...
they maintain that these are containers and it's only a matter of confusion: https://twitter.com/spoonapps/status/538038020755456000 looking forward to clearer documentation if that's the case
> Because containers are built on the Spoon virtualization engine, rather than simply providing an interface to container support in an underlying operating system, Spoon can containerize applications across multiple operating systems and provide advanced virtualization primitives. That means it's not containerization, but virtualization. This hardly compares to the Docker world which offers a intermediate build syst…
> That means it's not containerization, but virtualization. See above response. > This hardly compares to the Docker world which offers a intermediate build system (edit: Spoon has a build system however), rich command line tools (edit: it does provide some command line tools) to work with images and containers, fast spin up times, and an ecosystem of container management tools. The Spoon build system and command lin…