> Yes critical to this is to get the graphdriver (COW File Systems) out as a separate package. graphc so to speak. We are working on this.
awesome! > What would we need next to save a layered image? from https://runc.io/ it says "runC does not create a daemon, so it integrates well with systemd." so then we need make use of systemd @ magic (or maybe systemd-machined) and map dbus events into docker-like HTTP REST API and we would have drop-in replacement for example $ docker run -d myrepo/myapp 123abcdef123 will just create some bookkeeping files then systemctl start mywrapper@ 123abcdef123 =============== I don't like the idea of having moving parts inside docker daemon, I believe we should reach a point where it's sole job is to delegate the container running to systemd here is an example of docker daemon crashing and all running containers die for a silly glitch in my 3G connection https://github.com/docker/docker/issues/15328 On Sat, Oct 31, 2015 at 11:56 AM, Daniel J Walsh <dwa...@redhat.com> wrote: > Yes critical to this is to get the graphdriver (COW File Systems) out as a > separate package. graphc so to speak. We > are working on this. > > Once you have graphc you can mount up an image in any of the backends that > Docker supports, Devmapper, Btrfs, > overlayfs and run a container on them. What would we need next to save a > layered image? > > > On 10/30/2015 05:15 PM, Muayyad AlSadi wrote: > > > this using runc? > ok let it be runc instead of lxc > > so can we have docker-like dockerlite with *devicemapper* and runc ? > > the idea would be to make use of docker way of saving space with layers > ..etc. (running several containers from same image, saving space by layers > ..etc.) > and support the rich community of images and the ecosystem of build-tools > > > > > > > On Fri, Oct 30, 2015 at 11:08 PM, Daniel J Walsh <dwa...@redhat.com> > wrote: > >> >> >> On 10/30/2015 04:58 PM, Muayyad AlSadi wrote: >> > Hi, >> > >> > dockerlite is way to provide minimal docker features using scripts on >> > btrfs and lxc >> > >> > https://github.com/docker/dockerlite >> > >> > maybe it was aimed to demonstrate how simple docker can be implemented. >> > but I like that the idea of having containers independent of the daemon >> > (ie. we can run non-root containers and containers do not die when the >> > daemon restarted) >> > >> > I like to see such project that uses >> > >> > 1. device mapper instead of btrfs >> > 2. use systemd-nspawn instead of lxc >> > 3. use systemd's @ and dbus >> > >> > for example docker events api can be implemented as wrapper of dbus >> > >> > docker run -d foo >> > >> > will redirect to >> > >> > echo "whatever=whatever" > /etc/sysconfig/dockerlite/123.rc >> > systemctl start dockerlite@123.service >> > >> > >> > >> This looks kind of dead, why not look at implementing something like >> this using runc? >> >> > >
