Bug: REPL exits immediately about surrealdb

[spookyvision]

you need to tell Docker to attach an interactive termina

of course, silly me. Might be worth a sentence in the docs but yeah, in retrospect it's obvious :) closing.

[naisofly]

@spookyvision, If you have docker running first and are then following the steps in the docs on Run with Docker, this should work for you.

Can you kindly confirm you have

1. Docker Running
2. Run the steps mentioned in the docs above?

[spookyvision]

I can confirm it's not an issue of the docker db not running or a wrong connection parameter, because then I get this instead (using -e to force an invalid endpoint):

❯ docker run --rm --net=host --pull always surrealdb/surrealdb:latest sql --namespace demo --database demo -e 'ws://localhost:12345'
latest: Pulling from surrealdb/surrealdb
Digest: sha256:bc6d4b37fc79b8e4e93ab5630862e5211668a10a3302bad23bdc27a415b782f2
Status: Image is up to date for surrealdb/surrealdb:latest
2024-05-24T17:56:31.409609Z ERROR surreal::cli: There was a problem with the database: There was an error processing a remote WS request: IO error: Connection refused (os error 111)

To further clarify: I get the same buggy "instant quit" behavior whether I supply no -e parameter at all, or the assumed default -e ws://localhost:8000, where the DB is running.

I can also use the database from both the python and Rust SDKs fine.
Do I have to add authentication for the REPL to work? (that would surprise me, but I can surely give it a try)

[goosethedev]

To use the REPL with the sql command, you need to tell Docker to attach an interactive terminal after running the container. Try doing docker run -it .... Also check docker run --help for details on the -i and -t options.

The REPL itself doesn't need auth AFAIK but you won't be able to interact with any table. To clarify, sql connects you to an existing SurrealDB instance, whether spawned by Surrealist or another terminal running the start command as presented in the docs.