|Number of watchers on Github||482|
|Number of open issues||2|
|Average time to close an issue||6 months|
|Average time to merge a PR||less than a minute|
|Open pull requests||1+|
|Closed pull requests||0+|
|Last commit||almost 6 years ago|
|Repo Created||over 6 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||docker|
|Do you use dockerlite? Leave a review!|
|View open issues (2)|
|View dockerlite activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Dockerlite lets you run Linux apps in lightweight, isolated environments, using LXC (Linux Containers). It is inspired by Docker and it actually reimplements some of its most basic features.
Using BTRFS snapshots,
dockerlite can save the state of a given environment
in a frozen
image, and later, create more environments (
of that image.
It was inspired by Docker, and aims at being a sandbox to experiment new concepts linked with the Docker project.
It is not a replacement for Docker. It is missing (at least) the following features:
Its main feature is
HACKABILITY: 9000 since it's shell, and everybody
including your dog can write shell scripts, right?
A Linux container looks like a virtual machine: it has its own network stack, IP address, process space; it is isolated from its sibling containers (it can't see them and can't be seen by them). However, it runs on top of the same kernel as its host. This means that if your machine runs Linux 3.8, all containers on this machine will also run Linux 3.8. You cannot run another kernel (or another OS) within a container. Of course, you could run a full virtual machine within qemu or kvm within a container, but that's a different story!
dockerlite is a
light version of Docker.
The latter has similar features, but with the following major differences:
dockerliteis a Posix Shell script;
dockerlitedoes not run in the background.
Docker also has some extra features to store images in 3rd party services.
dockerlite initially targetted the following goals:
hackability, i.e. a lightweight testbed for new features which can be more cumbersome to implement in a full-blown Go project;
The first goal is loosely defined, depending on what you want to put in
core features of Docker. If you just want to create images and
misson complete. If you want to push/pull and use
a REST API, it's a long shot.
The other goals were met. Dockerlite confirmed that BTRFS was an acceptable option and that there were no unplanned side-effect or shotstopper preventing its use for Docker containers. It also served to evaluate different ways to setup the containers networking stack.
Apache 2 License
For JSON.sh license, see https://github.com/dominictarr/JSON.sh