Re: Problem running AtomGraph/fuseki-docker
Re: command prompt closure That’s standard Docker behaviour. Unless you tell it otherwise it runs your container in the foreground attached to your terminal. Also, you’ve specified --rm which tells Docker to remove the container as soon as it exits, if you want to inspect logs after the container exits don’t include this option. You probably wanted to add -d/--detach to run the container in the background, you can then follow the logs with the docker logs command or by viewing them in the Docker Desktop interface. Rob From: Steve Vestal Date: Wednesday, 6 December 2023 at 23:56 To: users@jena.apache.org Subject: Re: Problem running AtomGraph/fuseki-docker I was using bash. When I run it in command prompt, it works. Thanks! Interestingly, when the command prompt is closed, the container is removed from Docker Desktop. Each new start creates a new container with a new amusing name :-) C:\Users\svestal>docker run --rm -p 3030:3030 atomgraph/fuseki --mem '/ds' [2023-12-06 22:19:53] INFO Server :: Apache Jena Fuseki 4.6.1 [2023-12-06 22:19:53] INFO Server :: Database: in-memory [2023-12-06 22:19:53] INFO Server :: Path = /'/ds' [2023-12-06 22:19:53] INFO Server :: System [2023-12-06 22:19:53] INFO Server :: Memory: 2.0 GiB [2023-12-06 22:19:53] INFO Server :: Java: 17-ea [2023-12-06 22:19:53] INFO Server :: OS: Linux 5.15.133.1-microsoft-standard-WSL2 amd64 [2023-12-06 22:19:53] INFO Server :: PID:1 [2023-12-06 22:19:53] INFO Server :: Start Fuseki (http=3030) On 12/6/2023 2:12 PM, Martynas Jusevičius wrote: > Hi Steve, > > This looks like Windows shell issue. > > For some reason /ds is resolved as a filepath where it shouldn’t. > > Can you try —mem '/ds' with quotes? > > I’m running Docker on WSL2 and never had this problem. > > Martynas > > On Wed, 6 Dec 2023 at 21.05, Steve Vestal wrote: > >> I am running a VM with Microsoft Windows Server 2019 (64-bit). When I >> try to stand up the docker server, I get >> >> $ docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds >> String '/C:/Program Files/Git/ds' not valid as 'service' >> >> Suggestions? >> >>
Re: Problem running AtomGraph/fuseki-docker
[2023-12-06 22:19:53] INFO Server :: Path = /'/ds' Not good. Shell quoting didn't happen. That's a URL path component called '/ds' in the server root. Andy On 06/12/2023 23:55, Steve Vestal wrote: I was using bash. When I run it in command prompt, it works. Thanks! Interestingly, when the command prompt is closed, the container is removed from Docker Desktop. Each new start creates a new container with a new amusing name :-) C:\Users\svestal>docker run --rm -p 3030:3030 atomgraph/fuseki --mem '/ds' [2023-12-06 22:19:53] INFO Server :: Apache Jena Fuseki 4.6.1 [2023-12-06 22:19:53] INFO Server :: Database: in-memory [2023-12-06 22:19:53] INFO Server :: Path = /'/ds' [2023-12-06 22:19:53] INFO Server :: System [2023-12-06 22:19:53] INFO Server :: Memory: 2.0 GiB [2023-12-06 22:19:53] INFO Server :: Java: 17-ea [2023-12-06 22:19:53] INFO Server :: OS: Linux 5.15.133.1-microsoft-standard-WSL2 amd64 [2023-12-06 22:19:53] INFO Server :: PID: 1 [2023-12-06 22:19:53] INFO Server :: Start Fuseki (http=3030) On 12/6/2023 2:12 PM, Martynas Jusevičius wrote: Hi Steve, This looks like Windows shell issue. For some reason /ds is resolved as a filepath where it shouldn’t. Can you try —mem '/ds' with quotes? I’m running Docker on WSL2 and never had this problem. Martynas On Wed, 6 Dec 2023 at 21.05, Steve Vestal wrote: I am running a VM with Microsoft Windows Server 2019 (64-bit). When I try to stand up the docker server, I get $ docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds String '/C:/Program Files/Git/ds' not valid as 'service' Suggestions?
Re: Problem running AtomGraph/fuseki-docker
I was using bash. When I run it in command prompt, it works. Thanks! Interestingly, when the command prompt is closed, the container is removed from Docker Desktop. Each new start creates a new container with a new amusing name :-) C:\Users\svestal>docker run --rm -p 3030:3030 atomgraph/fuseki --mem '/ds' [2023-12-06 22:19:53] INFO Server :: Apache Jena Fuseki 4.6.1 [2023-12-06 22:19:53] INFO Server :: Database: in-memory [2023-12-06 22:19:53] INFO Server :: Path = /'/ds' [2023-12-06 22:19:53] INFO Server :: System [2023-12-06 22:19:53] INFO Server :: Memory: 2.0 GiB [2023-12-06 22:19:53] INFO Server :: Java: 17-ea [2023-12-06 22:19:53] INFO Server :: OS: Linux 5.15.133.1-microsoft-standard-WSL2 amd64 [2023-12-06 22:19:53] INFO Server :: PID: 1 [2023-12-06 22:19:53] INFO Server :: Start Fuseki (http=3030) On 12/6/2023 2:12 PM, Martynas Jusevičius wrote: Hi Steve, This looks like Windows shell issue. For some reason /ds is resolved as a filepath where it shouldn’t. Can you try —mem '/ds' with quotes? I’m running Docker on WSL2 and never had this problem. Martynas On Wed, 6 Dec 2023 at 21.05, Steve Vestal wrote: I am running a VM with Microsoft Windows Server 2019 (64-bit). When I try to stand up the docker server, I get $ docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds String '/C:/Program Files/Git/ds' not valid as 'service' Suggestions?
Re: Problem running AtomGraph/fuseki-docker
Hi Steve, This looks like Windows shell issue. For some reason /ds is resolved as a filepath where it shouldn’t. Can you try —mem '/ds' with quotes? I’m running Docker on WSL2 and never had this problem. Martynas On Wed, 6 Dec 2023 at 21.05, Steve Vestal wrote: > I am running a VM with Microsoft Windows Server 2019 (64-bit). When I > try to stand up the docker server, I get > > $ docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds > String '/C:/Program Files/Git/ds' not valid as 'service' > > Suggestions? > >
Problem running AtomGraph/fuseki-docker
I am running a VM with Microsoft Windows Server 2019 (64-bit). When I try to stand up the docker server, I get $ docker run --rm -p 3030:3030 atomgraph/fuseki --mem /ds String '/C:/Program Files/Git/ds' not valid as 'service' Suggestions?
