Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: jkn Newsgroups: comp.lang.forth Subject: Re: GForth in Docker. Date: Tue, 4 Aug 2026 22:50:03 +0100 Lines: 29 Message-ID: References: <114tl3v$2fsah$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net sKvb9X3DJUh3ZdW71K8A0wySPWMPXBY+3BuvW1FK4gouZUN/yM Cancel-Lock: sha1:KGz7m6z6Qocn92zNLoezVDydMAE= sha256:yNMdup1sc93VuasrdHu6G76nCMZrhcFDx095q5Y8CF0= User-Agent: Mozilla Thunderbird Content-Language: en-US In-Reply-To: <114tl3v$2fsah$1@dont-email.me> Xref: csiph.com comp.lang.forth:135295 On 04/08/2026 22:21, Nick P wrote: > Hi all, Im new here. > > Having checked out the GForth.org webpage I have gone with the "use > docker" option (on Ubuntu 22.04). As a result I'm having difficulty > getting .fs files I have on one of my hard drives to run in it. > > I can get the docker image running, and use the command line without a > problem, what I cant do is run a file that is in some arbitary directory > on a disk. > > I strongly suspect its a docker issue rather than a Gforth issue as the > Gforth site and documentation does not cover this so far as I can tell. > > Does anyone have a suggestion of a source of information, jargon lite > hopefully, that will get me started using source files with GForth in a > docker container? What do you mean by 'can't run...'? What did you try, and what happened? I would expect that your 'docker run' command should include parameters to map directory/ies on your host machine, to those in the running docker container. Then, the GForth running in the latter will be able to see your existing Forth files. Does that help any? J^n