docker-mailserver: 2.3 Issues Thread - master.lock: cannot open file: Permission denied
The mail system starts up with docker-compose up -d - however,
port 25 and 587 refuse a connection while other (e.g. 143 (IMAP)) work.
The postfix service isn’t running at all, in container in
‘/var/log/mail/mail.err’ (and ‘[…]mail.log’) postfix logged an error:
postfix/master[1093]: fatal: open lock file /var/lib/postfix/master.lock: cannot open file: Permission denied
When this happens there should be at least an error logged to docker or startup cancelled.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 29 (19 by maintainers)
Commits related to this issue
- This should fix most of 2.3 issues reported in #545 & 586 — committed to docker-mailserver/docker-mailserver by tomav 7 years ago
- This should fix most of 2.3 issues reported in #545 & #586 (#612) * Fixes most of 2.3 issues reported in #545 & 586 — committed to docker-mailserver/docker-mailserver by tomav 7 years ago
- This should fix most of 2.3 issues reported in #545 & #586 (#612) * Fixes most of 2.3 issues reported in #545 & 586 — committed to RichardFevrier/docker-mailserver by tomav 7 years ago
Hi, I face the same issue since the last update, so I think it would be a really good idea to add a permission check at startup 😃
regards
Of course. But I had already pulled the 2.3 tag version before the fix was applied. So once fixed has been deployed to same 2.3 tag then a new pull request of 2.3 was looking first in my local cache rather than on hub and so not retrieving the fixed 2.3 version.
Build available with
:2.3tag.@tomav: One improvement would be already if Dovecot logs to container stdout/logs. Using a process/service manager like supervisord or chaperone.d would allow proper exit in case of errors.
Want to add this check on startup?