Repository navigation
Replies: 2 comments
|
Hi @tep1997 , your postgres container is meant to have its data volume either mounted or not removed when your doing docker docker compose down. if the volume is removed or the data path is not mapped to a local path, the data will remain inside the container and just reset when the container is replaced . Specifically |
0 replies
|
Found it. I had an incorrect mount syntax pointing at an old Portainer
instance from a recent migration.
All good now, thanks!
…On Tue, Sep 8, 2026 at 11:53 AM Thegan Govender ***@***.***> wrote:
Hi @tep1997 <https://github.com/tep1997> , your postgres container is
meant to have its data volume either mounted or not removed when your doing
docker docker compose down. if the volume is removed or the data path is
not mapped to a local path. the data remains inside the container and just
resets when the container is replaced . Specifically /var/lib/postgresql
in your postgres container needs to be mounted
—
Reply to this email directly, view it on GitHub
<#548?email_source=notifications&email_token=AOW2JNQMQ4Y2RXW2MHGE4AT5OATO5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGUZDKMZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18352539>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOW2JNSP5NAFIOFX7IV26F35OATO5AVCNFSNUABIKJSXA33TNF2G64TZHM3DCMJQHEZDEOBXHNCGS43DOVZXG2LPNY5TCMBXG42TQNRSUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AOW2JNSRVBUVST3JSWRNZIL5OATO5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGUZDKMZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/AOW2JNS5UDRJN6GSPEHU3IL5OATO5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGUZDKMZZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Todd
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What is the proper way to upgrade without losing historical data? I just ran a docker compose down and then docker compose pull to upgrade to newest. When it finished, I had the new version but no historical data.
All reactions