-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash starting as non-root Docker container: SQLite3::ReadOnlyException: attempt to write a readonly database #300
Comments
@meonkeys does it work after you remove -u 1001:1001 ? |
Yes. |
What's the resolution? fixed / won't fix / not an issue / etc.? |
@meonkeys please reopen with more details if you still have any issues deploying (i thought 'yes' means that the issue has been fixed by removing the -u flag) |
Ah, cool. And thanks--I was able to deploy (in a non-root container) by manually creating my own I agree omitting |
@meonkeys the reported issue is not related to the docuseal app - it's related to linux/docker configurations and permissions |
I'm trying to get 1.6.2 running in Docker with sqlite in a non-root container. Is this supported?
docuseal/docuseal:1.6.2
docker-buildx
version0.12.1-0ubuntu1~22.04.1
installedRepro steps:
sudo groupadd e-sign
(got uid 1001)sudo useradd --shell /usr/sbin/nologin --no-create-home --gid e-sign e-sign
(got gid 1001)docker run --rm -it --name docuseal -p 3000:3000 -u 1001:1001 -v e-sign:/data docuseal/docuseal
I'm expecting it to create a default
docuseal.env
file and sqlite files in/data/docuseal/
, but instead I'm seeing this:(click to expand)
The text was updated successfully, but these errors were encountered: