When create a new lucky app, the postgres_data volume never work as expected.

[zw963]

When create a new lucky app, will create a docker-compose.yml like this

    volumes:
      - type: volume
        source: postgres_data
        target: /var/lib/postgresql

But above code never work, because postgres offical Dockerfile create a new volume early from /var/lib/postgresql/data, which cause latter bind mount from /var/lib/postgresql always a empty data folder, because data folder below /var/lib/postgresql is a mounted volume.

if check docker inspect, you can see two mount point.

        "Mounts": [
            {
                "Type": "volume",
                "Name": "clover_postgres_data",
                "Source": "/docker/containers/volumes/clover_postgres_data/_data",
                "Destination": "/var/lib/postgresql",
                "Driver": "local",
                "Mode": "z",
                "RW": true,
                "Propagation": ""
            },
            {
                "Type": "volume",
                "Name": "1e7cb97e7e08dbd0f38dd4855e19e7e5497afc50dcf7bd4d1819b2e06716593d",
                "Source": "/docker/containers/volumes/1e7cb97e7e08dbd0f38dd4855e19e7e5497afc50dcf7bd4d1819b2e06716593d/_data",
                "Destination": "/var/lib/postgresql/data",
                "Driver": "local",
                "Mode": "",
                "RW": true,
                "Propagation": ""
            }
        ],

The fix is quite simple, just change target: /var/lib/postgresql into target: /var/lib/postgresql/data.

I give some advice in discuss here too, but, i guess someone miss this question. 😄

If consider accept contribute on those changes, i will create a PR for fix this.

[zw963]

BTW: to verify the volume postgres_data never work, you can try:

1. docker-compose up
2. create a record.
3. docker-compose down to remove postgres container.
4. docker-compose up again.
5. your's record disappear ...

because db data never save to a referenceable volume ... when you docker-compose up again, it created a new dangling value instead, that will create many disk space, and produce unused data.

[jwoertink]

Sure, you can send a PR for that fix. I think that makes sense 👍