mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 08:45:54 +03:00
[GH-ISSUE #134] Docker Image fails to run with MP_DATA_FILE set #92
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#92
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tminich on GitHub (Jun 28, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/134
First let me prefix that I'm not well-versed in Docker, so this might be because I'm doing something wrong. But, to my understanding of the docs, this should be working.
Here is the service from my
docker-compose.yml:The service keeps restarting logging
@axllent commented on GitHub (Jun 28, 2023):
I got the same ~ though
- MP_DATA_FILE=/data/mailpit.db(without quotes) works fine. It must be a docker-compose thing :)@axllent commented on GitHub (Jun 28, 2023):
I don't use docker-compose - but from what I read the syntax should actually be different: https://docs.docker.com/get-started/08_using_compose/
@tminich commented on GitHub (Jun 28, 2023):
Ah thanks, I did not expect that to matter XD.
@mbuchner commented on GitHub (Apr 20, 2024):
Don't think this is only the configuration style - since v1.15.1it is also not working for me. I didn't test v1.16.
v1.17.0 also displays this error to me - same setting worked with v1.15.1!
I use it with compose:
and Kubernetes:
Both are not working anymore - showing:
time="2024/04/20 19:09:13" level=error msg="[db] unable to open database file: out of memory (14)"
When I disable the setting "MP_DATABASE" and just keep the rest -> everything works fine
@axllent commented on GitHub (Apr 20, 2024):
@mbuchner Oh no, that's not good. Does the
/datadirectory exist and is it local and writeable? Please open a new issue if you are unable to resolve it.Edit: Confirmed - you do not have a volume in
/datain your container, so that path does not exist and Mailpit fails to create the database. I will be updating the error messages to make these kinds of things clearer, however in the meantime please see the example on https://mailpit.axllent.org/docs/install/docker/ which includes the volume in the config.@mbuchner commented on GitHub (Apr 22, 2024):
The thing is that I don’t want a volume (don’t have a volume) available - I just wanted a "persistent" DB as long as it is the same container ... DB survives normal restarts - but gets cleaned when image / container is recreated ...
Probably /tmp/mailpit.db works - I will test ...
+1 for improving the error message ;-)