Re: postgres and initdb not working inside docker
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Roffild <roffild@hotmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-05-28T15:51:32Z
Lists: pgsql-hackers
> On 28 May 2022, at 17:49, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Daniel Gustafsson <daniel@yesql.se> writes: >>> On 28 May 2022, at 14:59, Roffild <roffild@hotmail.com> wrote: >>> This patch fixes an issue inside Docker and will not affect other builds. > >> Looks like you generated the patch backwards, it's removing the lines you >> propose to add. > > Lacks documentation, too. But it doesn't matter, because we are not > going to accept such a "feature". The OP has offered no justification > why this is necessary (and no, he's not the first who's ever used > Postgres inside Docker). Introducing a security hole that goes > against twenty-five years of deliberate project policy is going to > require a heck of a lot better-reasoned argument than "there's an > issue inside Docker". FWIW, I 100% agree. -- Daniel Gustafsson https://vmware.com/