Feedback-ID: ie3de48e3:Fastmail
Date: Thu, 16 Oct 2025 19:27:12 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: mckeny@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19089: Mounting Issue
Message-ID: <202510161641.r6oqnu4dpklb@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <19089-c28315ab89f9ced4@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/202510161641.r6oqnu4dpklb%40alvherre.pgsql>
Precedence: bulk

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/