Re: Announcement: PicoLisp in a docker container

[David Bloom]

It's not nearly that cool yet.  I must have updated the version without
updating the docs a while back. While updating the docs I noticed that
there's yet a newer version out.

Isn't there already a script somewhere that pings the download page of
picolisp.com for a newer version?  I'd like to stay on top of versioning.
I'm new to maintaining an open source product and strive to one day meet
the responsiveness and helpfulness that many others have been to me in this
forum.

-David

On Aug 22, 2016 5:15 AM, "Jon Kleiser"  wrote:

> Thanks again, David!
>
> When I run this and do “(version)”, I get 16.5.30, while your docs says
> “This is version 16.2”. I guess one gets the current stable release version
> when one does the “docker pull”. Is that right?
>
> /Jon
>
> > On 22. Aug, 2016, at 02:00, David Bloom  wrote:
> >
> > Docs updated.  Sorry it took me so long.  I'll be quicker to respond in
> the future.  Added a --rm to automatically remove the container upon exit

Re: Announcement: PicoLisp in a docker container

[Jon Kleiser]

Thanks again, David!

When I run this and do “(version)”, I get 16.5.30, while your docs says “This 
is version 16.2”. I guess one gets the current stable release version when one 
does the “docker pull”. Is that right?

/Jon

> On 22. Aug, 2016, at 02:00, David Bloom  wrote:
> 
> Docs updated.  Sorry it took me so long.  I'll be quicker to respond in the 
> future.  Added a --rm to automatically remove the container upon exit.  That 
> way you don't have to manually remove any cruft left over in docker ps -a.  
> Optionally you can decide not to use the --rm switch and be able to inspect 
> the container after exit.
> 
> https://hub.docker.com/r/progit/docker-tinycore-picolisp/
> 
> Enjoy!
> 
> On Mon, Aug 15, 2016 at 9:31 AM, Jon Kleiser  wrote:
> Thanks a lot, David!
> 
> /Jon
> 
> > On 15. Aug, 2016, at 13:57, David Bloom  wrote:
> >
> > Pardon the delay Jon,  I've been under extreme amounts of stress but not
> > for much longer.  I'll update the docs to reflect getting a Tinycore prompt
> > rather than just a REPL.
> >
> > On Aug 15, 2016 6:08 AM, "Jon Kleiser"  wrote:
> >
> >> I just want to report that my use of “docker run -v” was not correct. This
> >> works much better:
> >>
> >> docker run -v /Users/jkleiser/script:/opt/script -it
> >> progit/docker-tinycore-picolisp
> >>
> >> I can then do things like (dir "/opt/script") or (in "/opt/script/foo.sh"
> >> (echo)) from inside PicoLisp.
> >>
> >> /Jon
> >>
> >>> On 12. Aug, 2016, at 16:40, Jon Kleiser  wrote:
> >>>
> >>> Hi David,
> >>>
> >>> I have now tried your container as described at
> >> https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got
> >> PicoLisp version 16.5.30 running. Does your container allow me to get
> >> access to the Tinycore Linux command line?
> >>>
> >>> I need to load a PicoLisp file I have on my Mac. I have tried starting
> >> your container like this:
> >>> docker run -v /Users/jkleiser/script -it progit/docker-tinycore-picolisp
> >>> but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I
> >> just get NIL, so for some reason sharing the OS X file system with your
> >> container doesn’t work at the moment. Maybe the container has to be set up
> >> for the new ‘osxfs’ shared file system solution? I don’t know.
> >>>
> >>> If I could get at the Tinycore Linux CLI, then I could maybe get my
> >> PicoLisp file by use of wget or curl (if I put the file on the net first)
> 
> 

Re: Announcement: PicoLisp in a docker container

[David Bloom]

Docs updated.  Sorry it took me so long.  I'll be quicker to respond in the
future.  Added a --rm to automatically remove the container upon exit.
That way you don't have to manually remove any cruft left over in docker ps
-a.  Optionally you can decide not to use the --rm switch and be able to
inspect the container after exit.

https://hub.docker.com/r/progit/docker-tinycore-picolisp/

Enjoy!

On Mon, Aug 15, 2016 at 9:31 AM, Jon Kleiser  wrote:

> Thanks a lot, David!
>
> /Jon
>
> > On 15. Aug, 2016, at 13:57, David Bloom  wrote:
> >
> > Pardon the delay Jon,  I've been under extreme amounts of stress but not
> > for much longer.  I'll update the docs to reflect getting a Tinycore
> prompt
> > rather than just a REPL.
> >
> > On Aug 15, 2016 6:08 AM, "Jon Kleiser"  wrote:
> >
> >> I just want to report that my use of “docker run -v” was not correct.
> This
> >> works much better:
> >>
> >> docker run -v /Users/jkleiser/script:/opt/script -it
> >> progit/docker-tinycore-picolisp
> >>
> >> I can then do things like (dir "/opt/script") or (in
> "/opt/script/foo.sh"
> >> (echo)) from inside PicoLisp.
> >>
> >> /Jon
> >>
> >>> On 12. Aug, 2016, at 16:40, Jon Kleiser  wrote:
> >>>
> >>> Hi David,
> >>>
> >>> I have now tried your container as described at
> >> https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got
> >> PicoLisp version 16.5.30 running. Does your container allow me to get
> >> access to the Tinycore Linux command line?
> >>>
> >>> I need to load a PicoLisp file I have on my Mac. I have tried starting
> >> your container like this:
> >>> docker run -v /Users/jkleiser/script -it progit/docker-tinycore-
> picolisp
> >>> but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I
> >> just get NIL, so for some reason sharing the OS X file system with your
> >> container doesn’t work at the moment. Maybe the container has to be set
> up
> >> for the new ‘osxfs’ shared file system solution? I don’t know.
> >>>
> >>> If I could get at the Tinycore Linux CLI, then I could maybe get my
> >> PicoLisp file by use of wget or curl (if I put the file on the net
> first)
>
>

Re: Announcement: PicoLisp in a docker container

[Jon Kleiser]

Thanks a lot, David!

/Jon

> On 15. Aug, 2016, at 13:57, David Bloom  wrote:
> 
> Pardon the delay Jon,  I've been under extreme amounts of stress but not
> for much longer.  I'll update the docs to reflect getting a Tinycore prompt
> rather than just a REPL.
> 
> On Aug 15, 2016 6:08 AM, "Jon Kleiser"  wrote:
> 
>> I just want to report that my use of “docker run -v” was not correct. This
>> works much better:
>> 
>> docker run -v /Users/jkleiser/script:/opt/script -it
>> progit/docker-tinycore-picolisp
>> 
>> I can then do things like (dir "/opt/script") or (in "/opt/script/foo.sh"
>> (echo)) from inside PicoLisp.
>> 
>> /Jon
>> 
>>> On 12. Aug, 2016, at 16:40, Jon Kleiser  wrote:
>>> 
>>> Hi David,
>>> 
>>> I have now tried your container as described at
>> https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got
>> PicoLisp version 16.5.30 running. Does your container allow me to get
>> access to the Tinycore Linux command line?
>>> 
>>> I need to load a PicoLisp file I have on my Mac. I have tried starting
>> your container like this:
>>> docker run -v /Users/jkleiser/script -it progit/docker-tinycore-picolisp
>>> but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I
>> just get NIL, so for some reason sharing the OS X file system with your
>> container doesn’t work at the moment. Maybe the container has to be set up
>> for the new ‘osxfs’ shared file system solution? I don’t know.
>>> 
>>> If I could get at the Tinycore Linux CLI, then I could maybe get my
>> PicoLisp file by use of wget or curl (if I put the file on the net first)

Re: Announcement: PicoLisp in a docker container

[Jon Kleiser]

I just want to report that my use of “docker run -v” was not correct. This 
works much better:

docker run -v /Users/jkleiser/script:/opt/script -it 
progit/docker-tinycore-picolisp

I can then do things like (dir "/opt/script") or (in "/opt/script/foo.sh" 
(echo)) from inside PicoLisp.

/Jon

> On 12. Aug, 2016, at 16:40, Jon Kleiser  wrote:
> 
> Hi David,
> 
> I have now tried your container as described at 
> https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got PicoLisp 
> version 16.5.30 running. Does your container allow me to get access to the 
> Tinycore Linux command line?
> 
> I need to load a PicoLisp file I have on my Mac. I have tried starting your 
> container like this:
> docker run -v /Users/jkleiser/script -it progit/docker-tinycore-picolisp
> but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I just get 
> NIL, so for some reason sharing the OS X file system with your container 
> doesn’t work at the moment. Maybe the container has to be set up for the new 
> ‘osxfs’ shared file system solution? I don’t know.
> 
> If I could get at the Tinycore Linux CLI, then I could maybe get my PicoLisp 
> file by use of wget or curl (if I put the file on the net first).
> 
> /Jon
> 
> 
>> On 6. Jun, 2016, at 23:32, David Bloom  wrote:
>> 
>> Hi Alex,
>> 
>> There are several reasons why I've created PicoLisp in a container.
>> 
>> 1) The image has recently been trimmed down to 14MB.  The large image was 
>> just to get something out there and refine it shortly afterwards.
>> 2) I didn't know that there was an existing extension.  Is it the latest 
>> version?  All existing apt-get/tce-load solutions were off older versions.
>> 3) PicoLisp on windows isn't very straightforward to set up but Docker seems 
>> easier.  Perhaps it can help garner more windows attention?
>> 4) And the main reason why is to run PicoLisp apps against a distributed 
>> storage on Triton container infrastructure.  Ultimately because I think 
>> people are doing it wrong, using Python mainly for data science 
>> applications.  My friend said to show people what's the right way then.  I'd 
>> much rather use PicoLisp rather than Python for data science applications.  
>> Yes I understand that it lowers the barrier of entry for non-programmers but 
>> then companies wind up hiring programmers anyway so I'm reaching for my 
>> favorite language
>> 
>> I hope that explains things more.
>> 
>> Why download a 187MB file to "try" PicoLisp in Tinycore when you can just 
>> type: "tce-load -il picolisp" to download/install the 88KB extension ?
>> 
>> I'm sorry, I don't understand the purpose of this.
>> 
>> 
>> Alex
>> 
>> On Wed, Jun 1, 2016 at 2:46 PM, David Bloom  wrote:
>> Thanks to your collective help I'm pleased to announce the availability of 
>> PicoLisp in a docker container!  Now anyone with docker installed can try 
>> out 64-bit PicoLisp v16.2 running on Tinycore Linux by running:
>> 
>> docker pull progit/picolisp
>> 
>> The image is 187MB which I hope to trim further but this is already hundreds 
>> of MB less than most popular images.  I'll maintain the latest version in 
>> the container.
>> 
>> Please do offer up helpful suggestions if you have any and enjoy!
>> 
>> -David Bloom
>> 
>> 
> 
> PԔ � )mX�����zV�u�.n7��I칻�&

Re: Announcement: PicoLisp in a docker container

[Jon Kleiser]

Hi David,

I have now tried your container as described at 
https://hub.docker.com/r/progit/docker-tinycore-picolisp/, and I got PicoLisp 
version 16.5.30 running. Does your container allow me to get access to the 
Tinycore Linux command line?

I need to load a PicoLisp file I have on my Mac. I have tried starting your 
container like this:
docker run -v /Users/jkleiser/script -it progit/docker-tinycore-picolisp
but when I from inside PicoLisp do (dir "/Users/jkleiser/script”), I just get 
NIL, so for some reason sharing the OS X file system with your container 
doesn’t work at the moment. Maybe the container has to be set up for the new 
‘osxfs’ shared file system solution? I don’t know.

If I could get at the Tinycore Linux CLI, then I could maybe get my PicoLisp 
file by use of wget or curl (if I put the file on the net first).

/Jon


> On 6. Jun, 2016, at 23:32, David Bloom  wrote:
> 
> Hi Alex,
> 
> There are several reasons why I've created PicoLisp in a container.
> 
> 1) The image has recently been trimmed down to 14MB.  The large image was 
> just to get something out there and refine it shortly afterwards.
> 2) I didn't know that there was an existing extension.  Is it the latest 
> version?  All existing apt-get/tce-load solutions were off older versions.
> 3) PicoLisp on windows isn't very straightforward to set up but Docker seems 
> easier.  Perhaps it can help garner more windows attention?
> 4) And the main reason why is to run PicoLisp apps against a distributed 
> storage on Triton container infrastructure.  Ultimately because I think 
> people are doing it wrong, using Python mainly for data science applications. 
>  My friend said to show people what's the right way then.  I'd much rather 
> use PicoLisp rather than Python for data science applications.  Yes I 
> understand that it lowers the barrier of entry for non-programmers but then 
> companies wind up hiring programmers anyway so I'm reaching for my favorite 
> language
> 
> I hope that explains things more.
> 
> Why download a 187MB file to "try" PicoLisp in Tinycore when you can just 
> type: "tce-load -il picolisp" to download/install the 88KB extension ?
> 
> I'm sorry, I don't understand the purpose of this.
> 
> 
> Alex
> 
> On Wed, Jun 1, 2016 at 2:46 PM, David Bloom  wrote:
> Thanks to your collective help I'm pleased to announce the availability of 
> PicoLisp in a docker container!  Now anyone with docker installed can try out 
> 64-bit PicoLisp v16.2 running on Tinycore Linux by running:
> 
> docker pull progit/picolisp
> 
> The image is 187MB which I hope to trim further but this is already hundreds 
> of MB less than most popular images.  I'll maintain the latest version in the 
> container.
> 
> Please do offer up helpful suggestions if you have any and enjoy!
> 
> -David Bloom
> 
> 

PԔ � )mX�����zV�u�.n7�

Re: Announcement: PicoLisp in a docker container

[David Bloom]

Hi Alex,

There are several reasons why I've created PicoLisp in a container.

1) The image has recently been trimmed down to 14MB.  The large image was
just to get something out there and refine it shortly afterwards.
2) I didn't know that there was an existing extension.  Is it the latest
version?  All existing apt-get/tce-load solutions were off older versions.
3) PicoLisp on windows isn't very straightforward to set up but Docker
seems easier.  Perhaps it can help garner more windows attention?
4) And the main reason why is to run PicoLisp apps against a distributed
storage on Triton container infrastructure.  Ultimately because I think
people are doing it wrong, using Python mainly for data science
applications.  My friend said to show people what's the right way then.
I'd much rather use PicoLisp rather than Python for data science
applications.  Yes I understand that it lowers the barrier of entry for
non-programmers but then companies wind up hiring programmers anyway so I'm
reaching for my favorite language

I hope that explains things more.
Why download a 187MB file to "try" PicoLisp in Tinycore when you can just
type: "tce-load -il picolisp" to download/install the 88KB extension ?

I'm sorry, I don't understand the purpose of this.


Alex

On Wed, Jun 1, 2016 at 2:46 PM, David Bloom  wrote:

> Thanks to your collective help I'm pleased to announce the availability of
> PicoLisp in a docker container!  Now anyone with docker installed can try
> out 64-bit PicoLisp v16.2 running on Tinycore Linux by running:
>
> docker pull progit/picolisp
>
> The image is 187MB which I hope to trim further but this is already
> hundreds of MB less than most popular images.  I'll maintain the latest
> version in the container.
>
> Please do offer up helpful suggestions if you have any and enjoy!
>
> -David Bloom
>

Re: Announcement: PicoLisp in a docker container

[Vidyuth Kini]

"One small step for picolisp, a giant leap for computingkind" -- viKid




On Jun 1, 2016 at 4:46 AM, David Bloom  wrote:

Thanks to your collective help I'm pleased to announce the availability of
PicoLisp in a docker container!  Now anyone with docker installed can try
out 64-bit PicoLisp v16.2 running on Tinycore Linux by running:

docker pull progit/picolisp

The image is 187MB which I hope to trim further but this is already
hundreds of MB less than most popular images.  I'll maintain the latest
version in the container.

Please do offer up helpful suggestions if you have any and enjoy!

-David Bloom

Re: Announcement: PicoLisp in a docker container

[Mike]

create announce on reddit.com/r/lisp

> On 1 июня 2016 г., at 17:46, David Bloom  wrote:
> 
> Thanks to your collective help I'm pleased to announce the availability of 
> PicoLisp in a docker container!  Now anyone with docker installed can try out 
> 64-bit PicoLisp v16.2 running on Tinycore Linux by running:
> 
> docker pull progit/picolisp
> 
> The image is 187MB which I hope to trim further but this is already hundreds 
> of MB less than most popular images.  I'll maintain the latest version in the 
> container.
> 
> Please do offer up helpful suggestions if you have any and enjoy!
> 
> -David Bloom