Обсуждение: BUG #19089: Mounting Issue

The following bug has been logged on the website:

Bug reference:      19089
Logged by:          Jevgeni
Email address:      mckeny@gmail.com
PostgreSQL version: 18.0
Operating system:   DSM for Synology NAS
Description:

Dear postgres dev team,

to begin with: I am just a semi-professional synology user. I have tried to
go through your documentation, however not everything is clear for me, thus
I decided to report a bug even though there might be a solution described
there. Please feel free to wait for a more precise bug report, but I wanna
do my part to improve postgres and have to place my issue.

Now to the bug: My goal was to install a paperless ngx version with a
postgres DB on an synology NAS (DS920). With the following
docker-compose.yml I have downloaded and installed the newest version 18.
Since the synology has a container Manager as app, I dont have to dive into
any linux "sudo" language, just import an docker-compose file created by the
community and thats it.

Part of docker-compose.yml for postgres
"db:
    image: docker.io/library/postgres:17.6
    restart: unless-stopped
    volumes:
      - /volume1/docker/paperless/pgdata:/var/lib/postgresql/data"

When trying to start the container, I faced the following mounting issue:
"Start container paperless-db-1 failed: {"message":"failed to create task
for container: failed to create shim task: OCI runtime create failed: runc
create failed: unable to start container process: error during container
init: error mounting \"/volume1/docker/paperless/pgdata\" to rootfs at
\"/var/lib/postgresql/data\": change mount propagation through procfd: open
o_path procfd: open

/volume1/@docker/btrfs/subvolumes/f09606bf50bd944d6fa6cb04b29702120c1639298878114955ae09f6cfa5a0d4/var/lib/postgresql/data:
no such file or directory: unknown"}."

Changing to the version 17.6 fixed the issue.

Thanks a lot for the job you are doing!

On Wed, Oct 15, 2025 at 8:33 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> When trying to start the container, I faced the following mounting issue:

Hello! Thank you for the report and the work you've done to investigate it.

Unfortunately the Docker Postgres maintainers aren't the same group as
the upstream Postgres maintainers, and you're on the upstream bugs
list now. It looks like the Docker issue tracker is at

    https://github.com/docker-library/postgres

and luckily, I think the issue you've reported is already tracked there:

    https://github.com/docker-library/postgres/issues/1370

Hope this helps, and thanks again!

--Jacob

On 2025-Oct-15, PG Bug reporting form wrote:

> Now to the bug: My goal was to install a paperless ngx version with a
> postgres DB on an synology NAS (DS920). With the following
> docker-compose.yml I have downloaded and installed the newest version 18.
> Since the synology has a container Manager as app, I dont have to dive into
> any linux "sudo" language, just import an docker-compose file created by the
> community and thats it.

I think the key thing to realize here is that the Docker compose files
are not published by the Postgres project, but by the Docker project
themselves.  So this is not our bug, and as I understand, you need to
report it here:
https://github.com/docker-library/postgres
I suspect they're going to want to know exactly which flavor are you
running (which version of Debian or Alpine).

> Part of docker-compose.yml for postgres
> "db:
>     image: docker.io/library/postgres:17.6
>     restart: unless-stopped
>     volumes:
>       - /volume1/docker/paperless/pgdata:/var/lib/postgresql/data"
> 
> When trying to start the container, I faced the following mounting issue:
> "Start container paperless-db-1 failed: {"message":"failed to create task
> for container: failed to create shim task: OCI runtime create failed: runc
> create failed: unable to start container process: error during container
> init: error mounting \"/volume1/docker/paperless/pgdata\" to rootfs at
> \"/var/lib/postgresql/data\": change mount propagation through procfd: open
> o_path procfd: open
>
/volume1/@docker/btrfs/subvolumes/f09606bf50bd944d6fa6cb04b29702120c1639298878114955ae09f6cfa5a0d4/var/lib/postgresql/data:
> no such file or directory: unknown"}."

I have no idea what this means, but I'm sure the docker-library people
will.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/