Immich•3mo ago

Issue with extra anonymous volumes in backup container

Hi Immich team! 👋 I'm running Immich via Cosmos Cloud and noticed my immich-backup container (using prodrigestivill/postgres-backup-local) is creating two unexpected anonymous volumes with hash names instead of just the expected /db_dumps volume. Installation method: Cosmos Cloud using the official Immich servapp template Current volumes in backup container: ✅ immich-backup → /db_dumps (expected) ❌ 4cbf4e781c71e6cb4ccf973e3e461fbb7db5cf918b5e97deaf401d47cdb32ae8 → /backups ❌ 4186fbc88fd680879332c8df837c6f353d528e3898e7909d3ee1c94bffaf9df0 → /var/lib/postgresql/data Generated backup container config after installation:

json{
  "services": {
    "immich-backup": {
      "container_name": "immich-backup",
      "image": "prodrigestivill/postgres-backup-local",
      "environment": [
        "POSTGRES_HOST=immich-database",
        "POSTGRES_DB=immich",
        "POSTGRES_USER=immich-postgres",
        "POSTGRES_PASSWORD=xxxxxxxxxxxxxxxxxxx",
        "SCHEDULE=@daily",
        "BACKUP_KEEP_DAYS=7",
        "BACKUP_KEEP_WEEKS=4", 
        "BACKUP_KEEP_MONTHS=6",
        "BACKUP_DIR=/db_dumps",
        "PGDATA=/var/lib/postgresql/data"
      ],
      "volumes": [
        {
          "Type": "volume",
          "Source": "immich-backup",
          "Target": "/db_dumps"
        },
        {
          "Type": "volume", 
          "Source": "4cbf4e781c71e6cb4ccf973e3e461fbb7db5cf918b5e97deaf401d47cdb32ae8",
          "Target": "/backups"
        },
        {
          "Type": "volume",
          "Source": "4186fbc88fd680879332c8df837c6f353d528e3898e7909d3ee1c94bffaf9df0", 
          "Target": "/var/lib/postgresql/data"
        }
      ],
      "restart": "unless-stopped",
      "network_mode": "immich"
    }
  }
}

json{
  "services": {
    "immich-backup": {
      "container_name": "immich-backup",
      "image": "prodrigestivill/postgres-backup-local",
      "environment": [
        "POSTGRES_HOST=immich-database",
        "POSTGRES_DB=immich",
        "POSTGRES_USER=immich-postgres",
        "POSTGRES_PASSWORD=xxxxxxxxxxxxxxxxxxx",
        "SCHEDULE=@daily",
        "BACKUP_KEEP_DAYS=7",
        "BACKUP_KEEP_WEEKS=4", 
        "BACKUP_KEEP_MONTHS=6",
        "BACKUP_DIR=/db_dumps",
        "PGDATA=/var/lib/postgresql/data"
      ],
      "volumes": [
        {
          "Type": "volume",
          "Source": "immich-backup",
          "Target": "/db_dumps"
        },
        {
          "Type": "volume", 
          "Source": "4cbf4e781c71e6cb4ccf973e3e461fbb7db5cf918b5e97deaf401d47cdb32ae8",
          "Target": "/backups"
        },
        {
          "Type": "volume",
          "Source": "4186fbc88fd680879332c8df837c6f353d528e3898e7909d3ee1c94bffaf9df0", 
          "Target": "/var/lib/postgresql/data"
        }
      ],
      "restart": "unless-stopped",
      "network_mode": "immich"
    }
  }
}

Questions: look at below after the immich bot

18 Replies

Immich•3mo ago

:wave: Hey @Laauergaard, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:

LaauergaardOP•3mo ago

Questions: Should the backup container only mount /db_dumps according to the official docs? Are the /backups and /var/lib/postgresql/data mounts necessary or is this a configuration error? Is there something in the prodrigestivill/postgres-backup-local image that automatically creates these mounts? My setup: Immich version: v1.136.0 Deployment: Cosmos Cloud Backup image: prodrigestivill/postgres-backup-local Container creating anonymous volumes instead of using defined volume names According to your backup documentation, it looks like only /db_dumps should be needed, but the generated config shows 3 volume mounts after installation. The backup is working functionally, but these extra anonymous volumes are concerning from a maintenance perspective. Thanks for any guidance! 🙏

Mraedis•3mo ago

FYI Cosmos install isn't official

LaauergaardOP•3mo ago

but this working always.

Mraedis•3mo ago

You shouldn't be needing any volume mounts apart from the target of the dump (db_dumps), but I'm not sure what the Cosmos crowd has cooked up Sure, I'm just saying "Official Cosmos" means nothing, you might as well have found some random dropbox link with a bunch of container images in it 👀

bo0tzz•3mo ago

This doesn't sound like an issue with Immich at all?

Mraedis•3mo ago

Ah sorry I misunderstood your question here @Laauergaard , the db dumper containr has 2 unnamed volumes, that's normal

bo0tzz•3mo ago

But rather with that postgres backups image

LaauergaardOP•3mo ago

Yeah. but compose installation:

        "{ServiceName}-backup": {
            "container_name": "{ServiceName}-backup",
            "hostname": "{ServiceName}-backup",
            "image": "prodrigestivill/postgres-backup-local",
            "restart": "unless-stopped",
            "depends_on": {
                "{ServiceName}-database": {}
            },
            "environment": [
                "POSTGRES_HOST={ServiceName}-database",
                "POSTGRES_DB=immich",
                "POSTGRES_USER={ServiceName}-postgres",
                "POSTGRES_PASSWORD={Passwords.0}",
                "SCHEDULE=@daily",
                "BACKUP_KEEP_DAYS=7",
                "BACKUP_KEEP_WEEKS=4",
                "BACKUP_KEEP_MONTHS=6",
                "BACKUP_DIR=/db_dumps"
            ],
            "networks": {
                "{ServiceName}": {}
            },
            "network_mode": "{ServiceName}",
            "volumes": [
                {
                "type": "volume",
                "source": "{ServiceName}-backup",
                "target": "/db_dumps"
                }
            ],
            "if": "Context.installImmichBackup",
            "labels": {
                "cosmos-stack": "{ServiceName}",
                "cosmos-persistent-env": "POSTGRES_DB, POSTGRES_USER, POSTGRES_PASSWORD",
                "cosmos-auto-update": "true",
                "cosmos-icon": "https://ragdata.github.io/cosmos-servapps/servapps/immich/icon.png",
                "cosmos-force-network-mode": "{ServiceName}",
                "cosmos-force-network-secured": "true"
            }
        }
    },

        "{ServiceName}-backup": {
            "container_name": "{ServiceName}-backup",
            "hostname": "{ServiceName}-backup",
            "image": "prodrigestivill/postgres-backup-local",
            "restart": "unless-stopped",
            "depends_on": {
                "{ServiceName}-database": {}
            },
            "environment": [
                "POSTGRES_HOST={ServiceName}-database",
                "POSTGRES_DB=immich",
                "POSTGRES_USER={ServiceName}-postgres",
                "POSTGRES_PASSWORD={Passwords.0}",
                "SCHEDULE=@daily",
                "BACKUP_KEEP_DAYS=7",
                "BACKUP_KEEP_WEEKS=4",
                "BACKUP_KEEP_MONTHS=6",
                "BACKUP_DIR=/db_dumps"
            ],
            "networks": {
                "{ServiceName}": {}
            },
            "network_mode": "{ServiceName}",
            "volumes": [
                {
                "type": "volume",
                "source": "{ServiceName}-backup",
                "target": "/db_dumps"
                }
            ],
            "if": "Context.installImmichBackup",
            "labels": {
                "cosmos-stack": "{ServiceName}",
                "cosmos-persistent-env": "POSTGRES_DB, POSTGRES_USER, POSTGRES_PASSWORD",
                "cosmos-auto-update": "true",
                "cosmos-icon": "https://ragdata.github.io/cosmos-servapps/servapps/immich/icon.png",
                "cosmos-force-network-mode": "{ServiceName}",
                "cosmos-force-network-secured": "true"
            }
        }
    },

so I think the two unnamed volumes might need to be inserted?

Mraedis•3mo ago

LaauergaardOP•3mo ago

like this ?

"volumes": [
    {
        "type": "volume",
        "source": "{ServiceName}-backup",
        "target": "/db_dumps"
    },
    {
        "type": "volume", 
        "source": "{ServiceName}-backup-archive",
        "target": "/backups"
    },
    {
        "type": "volume",
        "source": "{ServiceName}-backup-temp",
        "target": "/var/lib/postgresql/data"
    }
]

"volumes": [
    {
        "type": "volume",
        "source": "{ServiceName}-backup",
        "target": "/db_dumps"
    },
    {
        "type": "volume", 
        "source": "{ServiceName}-backup-archive",
        "target": "/backups"
    },
    {
        "type": "volume",
        "source": "{ServiceName}-backup-temp",
        "target": "/var/lib/postgresql/data"
    }
]

Mraedis•3mo ago

LaauergaardOP•3mo ago

okay. Thanks for confirming! @bo0tzz Is this something that might be addressed in the future? Perhaps an official Immich backup solution that would only require the /db_dumps volume? Or should we expect to continue using third-party images like prodrigestivill/postgres-backup-local with their extra volume requirements?

Zeus•3mo ago

We already have builtin database dumps

Mraedis•3mo ago

We have an official backup, it writes to UPLOAD_LOCATION/backups

LaauergaardOP•3mo ago

Got it! Sounds like I should just remove the backup container from my compose then. No point in having the extra container when Immich handles it natively. Thanks for the clarification! 👍 Will switch to using the built-in backup feature instead.

Mraedis•3mo ago

Make sure your built-in works first before removing the external one

LaauergaardOP•3mo ago

I've started a new home server, so they're just deleted and started a new one. So I don't have any data in it.

Gaming

Programming

Issue with extra anonymous volumes in backup container

Did you find this page helpful?