Summing up Aleksa Sarai: tar isn’t well standardized, can be unpredictable, and is bad at random access and incremental updates. You’re likely of one of two mindsets about this: (1) that it’s extremely Unixy and thus excellent, or (2) that it’s extremely Unixy and thus horrifying. Pull the “config” JSON and you’ve got the entrypoint to run for the container you could, I guess, pull and run a Docker container with nothing but a shell script, which I’m probably the 1,000th person to point out. Unpack the tarballs in order and you’ve got the filesystem layout the container expects to run in. Start with some configuration by default, we’ll grab the base image for golang:įunction layers. You can write a shell script to pull a Docker container from its registry, and that might clarify. To rehydrate a container from its image, we just start the the first layer and unpack one on top of the next. A useful way to look at a Dockerfile is as a series of shell commands, each generating a tarball we call these “layers”. An OCI image is just a stack of tarballs.īacking up: most people build images from Dockerfiles. They do their best to make it look a lot more complicated, but OCI images - OCI is the standardized container format used by Docker - are pretty simple. So, instead, we transmogrify container images into Firecracker micro-VMs. Docker is great, but we’re high-density multitenant, and despite strides, Docker’s isolation isn’t strong enough for that. It’s pretty neat, and you should check it out with an already-working Docker container, you can be up and running on Fly in well under 10 minutes.Įven though most of our users deliver software to us as Docker containers, we don’t use Docker to run them. We take container images and run them on our hardware around the world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |