/db failed: No such device about datakit HOT 5 CLOSED

Is this expected behavior?

Not really :-) I think you forgot to run $ ./scripts/start-client.sh in your new terminal.

But as datakit just exposes a normal 9p endpoint, you can also just use a normal mount command, for instance:

sudo mount -t 9p -o trans=tcp,port=5640,noextend,nodev 127.0.0.1 /mnt/db

from datakit.

I'm hoping it is a user error on my part in reporting the bug. I thought that I had run $ ./scripts/start-client.sh. History shows that I did. Something else is going on.

I don't see any interesting logs. Where can I look?

from datakit.

The start-client.sh will start a new container. Please be sure you are running datakit-mount in the shell of that container.

But it's maybe an issue with the IP of the container running Datakit. Can you try to ping db to get the right IP address of the DB and use it to all the mount script: datakit -h <IP>?

from datakit.

I've tried to simplify the "quick start" steps. Now the following should just work:

docker network create datakit-net
docker run -d --net datakit-net --name datakit -v <path/to/git/repo>:/data docker/datakit
docker run -it --net datakit-net --privileged docker/datakit:client
ls /db

Thanks for the feedback and let me know if you have more issues!

from datakit.

@josephwinston hopefully the doc is now clearer. I'm going to close that issue now, but please re-open it if you still have issues/questions!

from datakit.