Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #135531

Re: GForth in Docker.

From Kragen Javier Sitaker <kragen@canonical.org>
Newsgroups comp.lang.forth
Subject Re: GForth in Docker.
Date 2026-09-02 14:26 -0300
Organization Primarily biological and memetic
Message-ID <87o6ef7efh.fsf@debian> (permalink)
References <114tl3v$2fsah$1@dont-email.me> <ndf54bF762U1@mid.individual.net> <0b4d65eb-5cb9-4b9d-9a54-df5f0a99b458@gmail.com> <2026Aug5.083504@mips.complang.tuwien.ac.at>

Show all headers | View raw


anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
> Nick P <nick.268@gmail.com> writes:
>>    sudo docker run -it \
>>     -v "$PWD":/usr/src/myapp \
>>     -w /usr/src/myapp \
>>     forthy42/gforth gforth fac1.fs -e bye
>
> Container technologies like Docker try to isolate the stuff inside the
> container from the outside, in order to protect the outside from
> whatever may go wild inside the container.  (...) if you use Docker,
> you get it and have to tell it where to drop the isolation.

Yes, this is the right answer in general.  Docker creates a little
isolated universe that can’t see the rest of your system, and you have
to explicitly specify what access it has to the rest of the system.
The `-v` flag is the easiest way to do that for the filesystem; `-p`
does it for network ports.

In Docker’s main use cases, this is more to protect the container from
the system than to protect the system from the container — it ensures
that what’s running inside the container doesn’t depend on your system C
library or your system installation of Python or whatever.  This is a
pretty big problem with things like Python: the “it works on my
machine!” problem.

Docker isn’t really intended or suited for interactive applications like
GForth, not really supporting X-Windows, D-Bus, etc.

Kragen

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

GForth in Docker. Nick P <nick.268@gmail.com> - 2026-08-04 22:21 +0100
  Re: GForth in Docker. jkn <jkn+nin@nicorp.co.uk> - 2026-08-04 22:50 +0100
    Re: GForth in Docker. Nick P <nick.268@gmail.com> - 2026-08-04 23:20 +0100
      Re: GForth in Docker. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-08-05 06:35 +0000
        Re: GForth in Docker. Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-02 14:26 -0300
  Re: GForth in Docker. albert@spenarnc.xs4all.nl - 2026-08-05 10:19 +0200
    Re: GForth in Docker. Colin Tree <treecolin@gmail.com> - 2026-08-06 08:47 +1000
      Re: GForth in Docker. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-08-06 05:08 +0000
        Re: GForth in Docker. albert@spenarnc.xs4all.nl - 2026-08-22 16:01 +0200

csiph-web