[ale] Docker containers as a desktop environment

[Alex Carver]

Right, I want to start from the base up and not rely on a public
repository.  That was the overall part of the question.  With a VM, you
spin up the VM and install your own OS inside it however you see fit
then install the software inside that OS however you see fit.  All the
Docker examples I find pull from public repositories but don't describe
standing something up from scratch.

On 2018-04-08 13:05, tosh noway wrote:
> You want to build your own OS ?
> 
> On Sun, Apr 8, 2018 at 4:05 PM Alex Carver <agcarver+ale at acarver.net> 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
>>>>
>>>
>>
>>
>