Would anyone know why the docker commands are now ...
# community-help
j
Would anyone know why the docker commands are now giving the error: "_invalid reference format._"? This occurs using the docker command in the example repo and with the command on the docker hub site's typesense page.
Copy code
docker run -i -p 8108:8108 -v`pwd`/typesense-server-data-1c/:/data typesense/typesense:0.24.0 --data-dir /data --api-key=xyz --listen-port 8108 --enable-cors
Answering my own question, it appears that…
Copy code
v`pwd`/
…Now needs to be:
Copy code
v"`pwd`"/
j
Interesting, wonder if it's a shell-specific thing. May I know what shell you're using?
j
Sure, using the default shell, OSX 14.4.1. /bin/zsh
j
Hmm, that's what I use... Seems to work for me
j
Ok, that's bizarre. Let me test again.
Below is a gist with the terminal output. First, I output the zsh version, then try to the command line with ``pwd`` . Then, I do the same command with `"`pwd`"` and TS starts. https://gist.github.com/JamesBurgoon/72afc71c60f3129640405e0cbac81d08
j
Hmmm, that exact command works fine for me Tried on both iTerm2 and also the built-in Terminal mac app
Wonder if it could be a docker issue somehow? I'm running this version:
Copy code
docker --version
Docker version 25.0.3, build 4debf41
j
Ah good catch: Running:
Docker version 26.0.0, build 2ae903e
and
Docker Desktop 4.29.0 (145265) is currently the newest version available.
j
I upgraded to the latest docker version and still don't see the issue! So strange
j
Ugh. Ok. I'm out of ideas.
Ok, The issue is caused when the pwd output path has a space:
my work/blah/foo/typesense-instantsearch-demo
(The "_my work_" dir name causes the issue.) Apparently the safer way to account for this is to use:
Copy code
"$(pwd)"
j
Ahhh! It sounds obvious once you mentioned it 🤦‍♂️ Will fix it across our docs
🙌 1