[ale] Docker containers as a desktop environment

Jim Kinney jim.kinney at gmail.com
Mon Apr 9 11:43:49 EDT 2018


https://docs.docker.com/develop/develop-images/baseimages/
You build from a dockerfile and add the line:
FROM scratch  # this means nothing, blank
-OR-
create a full image from a currently running OS using tar (debian has a
tool for this)
The CentOS mkimage-yum.sh script very distro specific and also very
capable. 
On Sun, 2018-04-08 at 13:04 -0700, Alex Carver via Ale wrote:
> Yes but not what I'm asking.  You're still pulling from a public
> repository.  I'm talking about making a container totally from
> scratch,
> no public repositories.
> 
> On 2018-04-08 12:13, tosh noway wrote:
> > https://docs.docker.com/engine/reference/builder/
> > 
> > FROM alpine:lastest
> > RUN echo “hello from docker”
> > 
> > On Sat, Apr 7, 2018 at 3:32 PM Alex Carver via Ale <ale at ale.org>
> > wrote:
> > 
> > > One thing I haven't been able to find is how to create a docker
> > > container in the first place from scratch.  Every tutorial has
> > > you
> > > downloading someone's container from somewhere.
> > > 
> > > If I wanted to experiment with running let's say a browser within
> > > a
> > > container on any OS, where can you go to find out how to build
> > > all of
> > > that?  At the moment I just spin up VM's but if containers really
> > > are a
> > > little lighter on the system than a full VM, I wouldn't mind
> > > trying it
> > > out just for browsers.
> > > 
> > > It seems to me, though, there's a slight inflexibility in the
> > > docker
> > > method versus VM method in terms of updating and/or
> > > modifications.  For
> > > example, if I create a brand new VM, install a bare OS and then
> > > install
> > > the browser, I can possibly go back in later and add something I
> > > forgot
> > > (e.g. Java, flash, etc.) just by using the guest OS's install
> > > methods.
> > > The new data is merged in right away and the next time I start
> > > that VM
> > > those changes are made.  My understanding with the Docker method
> > > is that
> > > everything has to be installed either in the original image or on
> > > the
> > > fly by the docker container script as the image starts but,
> > > again, this
> > > is relying on someone else's docker-ready stuff.
> > > 
> > > If anyone has pointers on this kind of thing I'd like to see them
> > > and
> > > try it out.
> > > _______________________________________________
> > > Ale mailing list
> > > Ale at ale.org
> > > https://mail.ale.org/mailman/listinfo/ale
> > > See JOBS, ANNOUNCE and SCHOOLS lists at
> > > http://mail.ale.org/mailman/listinfo
> > > 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> https://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
-- 
James P. Kinney III

Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain

http://heretothereideas.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20180409/d0de8819/attachment.html>


More information about the Ale mailing list