-
Notifications
You must be signed in to change notification settings - Fork 48
Permission failures when creating the database causes a segfault #105
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
Comments
I'll hop on this as soon as I can. This should be resolvable in the |
I haven't forgotten about this. Just a little swamped with work. |
No worries, this is an open source project after all. I don't have any expectations for a quick fix but I certainly do appreciate your thoughtfulness!! |
I've got a fix for this. Turns out tear down procedure was causing issues. The |
@ollien this will be released under |
Bet me to it. Thanks for this. |
😉 I finally got some free time today 😄 |
Summary
When putting together a project of mine, I was getting an unexplainable segfault for quite some time. After some digging, I noticed that it went away when my application was run as root in my Docker container, which hinted it might be permission related. Some googling later, I found this post on the Elixir Forum, which suggested the same; I eventually discovered that this was due to the fact that I was attempting to create a database in a directory where I did not have permission to do so.
Reproduction
mix ecto.create
(both produce this segfault)I have assembled a repo which contains a minimal project that can reproduce this issue. Note that I have pointed the repo to
/etc
, which on my system (and in most distros), is not writable by non-root users; you may need to change this to another location in order to perform the reproduction.I have successfully reproduced this both on my Fedora 36 system and a Debian 11 docker image.
Stacktrace
The text was updated successfully, but these errors were encountered: