improve docker docs

[AgustinRamiroDiaz]

fixes surrealdb/surrealdb#3468

Why

Docker file permissions are hard to understand, and cause trouble for newcomers. This PR adds an extra step to reduce the likelihood of errors for users.

Context

There's more context in the issue

Notes

I'm not a professional documentation creator, modify as you please

[netlify]

✅ Deploy Preview for surrealdb-docs ready!

Name	Link
🔨 Latest commit	057e1ed
🔍 Latest deploy log	https://app.netlify.com/sites/surrealdb-docs/deploys/65f45c2f849c8a00087e7840
😎 Deploy Preview	https://deploy-preview-315--surrealdb-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sgirones]

thanks for the PR @AgustinRamiroDiaz.

I would suggest using the -dev Docker image tags instead, which run as root by default (i.e. surrealdb/surrealdb:latest-dev)

That way there's no need to change the file ownership

[Ekwuno]

thanks for the PR @AgustinRamiroDiaz.

I would suggest using the -dev Docker image tags instead, which run as root by default (i.e. surrealdb/surrealdb:latest-dev)

That way there's no need to change the file ownership

+1 and the container will be based on. It's the latest-dev version of the surrealdb/surrealdb image.

[AgustinRamiroDiaz]

@sgirones thanks for the warm welcome :D

I understand that the dev image would solve it too. I guess you are proposing that to simplify the usability of the command. I think that this approach might look a bit "unprofessional" to users since we suggest to use a dev image when running docker (just my thoughts)

WDYT about adding --user root to the docker run command (while still using the production image) and then specify something like "if you are an advanced docker user you can remove the root user and set permissions in the container accordingly"

---

@Ekwuno sorry, I don't understand your comment. What does "the container will be based on" mean?

[Ekwuno]

@AgustinRamiroDiaz sorry about that. I mean that adding surrealdb/surrealdb:latest-dev means that the docker container will be based on the latest version of the surrealdb/surrealdb image