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 <[email protected]> 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?
