[GH-ISSUE #142] default docker-compose is not synced with default config #57

New issue

Closed

opened 2026-03-13 15:34:01 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 15:34:01 +03:00

Owner

Originally created by @kostyrev on GitHub (Feb 1, 2019).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/142

I've noticed that docker-compose config mounts data directory into /var/lib/acme-dns but default config does not uses it and that leads to data loss after container gets recreated.

Originally created by @kostyrev on GitHub (Feb 1, 2019). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/142 I've noticed that docker-compose config [mounts](https://github.com/joohoi/acme-dns/blob/master/docker-compose.yml#L15) data directory into `/var/lib/acme-dns` but default config [does not uses](https://github.com/joohoi/acme-dns/blob/master/config.cfg#L30) it and that leads to data loss after container gets recreated.

kerem closed this issue

2026-03-13 15:34:06 +03:00

kerem commented

2026-03-13 15:34:12 +03:00

Author

Owner

@joohoi commented on GitHub (Feb 1, 2019):

Oh, damn. You are completely right in this. Looks like a modification slipped in in commit f64de035 . This is completely a mistake from my side, I'll fix the default configuration file right away!

Thanks for opening issue!

@joohoi commented on GitHub (Feb 1, 2019): Oh, damn. You are completely right in this. Looks like a modification slipped in in commit f64de035 . This is completely a mistake from my side, I'll fix the default configuration file right away! Thanks for opening issue!