From rodrigoborgespereira at gmail.com Tue Dec 7 18:10:33 2021 From: rodrigoborgespereira at gmail.com (Rodrigo Borges Pereira) Date: Tue, 7 Dec 2021 18:10:33 +0000 Subject: [scl.org] Updates for rh-postgresql* packages Message-ID: Hello, There's been a number of CVE's issued for PostgreSQL, and they have released their own updated packages. Would it be possible to publish updated SCL rh-postgresql packages for the latest PGDG releases? I'm particularly interested in 12.9 and 10.19. Although I was able to build 10.19 by re-using the 10.17 SRPM and adjusting the sources files and SPEC, the same approach did not work for 12.9, it fails in the end due to some missing files. In the past I was able to build 12.7 like that (before it was published in SCL), but looks like some more magic is needed for 12.9. Thanks in advance, cheers Rodrigo -------------- next part -------------- An HTML attachment was scrubbed... URL: From jstanek at redhat.com Wed Dec 8 11:13:45 2021 From: jstanek at redhat.com (=?UTF-8?Q?Jan_Stan=C4=9Bk?=) Date: Wed, 8 Dec 2021 06:13:45 -0500 Subject: [scl.org] Updates for rh-postgresql* packages In-Reply-To: References: Message-ID: Hi Rodrigo, the rh-* collections are (usually) straight rebuilds of RedHat released packages; we generally try to avoid downstream patches. That being said, and given there were security releases from upstream, I would suspect the update is being worked on by RH right now. Once that releases, the CentOS rebuild will follow shortly. Best regards, -- Jan Stan?k Software Engineer, Red Hat jstanek at redhat.com irc: jstanek -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From rmarasch at redhat.com Wed Dec 15 09:16:00 2021 From: rmarasch at redhat.com (Ricardo Maraschini) Date: Wed, 15 Dec 2021 10:16:00 +0100 Subject: [scl.org] rhel-8/postgresql with huge pages Message-ID: Hello, When I attempt to use the image rhel8/postgresql-10 in an OpenShift 4.x cluster whose nodes have huge pages enabled it crashes with the following message: "running bootstrap script ... child process was terminated by signal 7: Bus error" This seems to be related to an existing issue [1]. My conclusion is that if I want to run this image in such a cluster I'm gonna need to disable huge pages in the postgres config, is that correct? What would be the correct way of doing this? I overwrote postgres sample config inside the image (added huge_pages=off to it) and that got postgres running but I still see a few bus errors during initdb (seems like initdb runs using an empty postgres config and I could not figure out a way of passing -c huge_pages=off to it). [1] https://github.com/opencontainers/runtime-spec/issues/1050 Thanks for your help, follow the full log I see when starting the image (without overwriting the sample config): The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.utf8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /var/lib/pgsql/data/userdata ... ok creating subdirectories ... ok selecting default max_connections ... sh: line 1: 22 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=100 -c shared_buffers=1000 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 24 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=50 -c shared_buffers=500 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 26 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=40 -c shared_buffers=400 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 28 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=30 -c shared_buffers=300 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 30 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=200 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 20 selecting default shared_buffers ... sh: line 1: 32 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=16384 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 34 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=8192 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 36 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=4096 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 38 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=3584 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 40 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=3072 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 42 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=2560 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 44 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=2048 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 46 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=1536 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 48 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=1000 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 50 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=900 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 52 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=800 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 54 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=700 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 56 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=600 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 58 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=500 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 60 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=400 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 62 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=300 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 64 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=200 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 66 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=100 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 sh: line 1: 68 Bus error (core dumped) "/usr/bin/postgres" --boot -x0 -F -c max_connections=20 -c shared_buffers=50 -c dynamic_shared_memory_type=none < "/dev/null" > "/dev/null" 2>&1 400kB selecting default timezone ... Etc/UTC selecting dynamic shared memory implementation ... posix creating configuration files ... ok running bootstrap script ... child process was terminated by signal 7: Bus error initdb: removing contents of data directory "/var/lib/pgsql/data/userdata" -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.gonzalez at redhat.com Fri Dec 10 22:37:12 2021 From: jose.gonzalez at redhat.com (Jose Gonzalez) Date: Fri, 10 Dec 2021 16:37:12 -0600 Subject: [scl.org] ubi8/nodejs-16-minimal HOME env and PATH Message-ID: Hi there! I attempted to use the ubi8/nodejs-16-minimal image ( https://catalog.redhat.com/software/containers/ubi8/nodejs-16-minimal/615aefd53f6014fa45ae1ae2) and couldn't seem to get the PATH to refer to the appropriate $HOME location. The result is that the node_modules paths are all relative to root ("/") instead of relative to the /opt/app-root/src path $ docker run -it registry.access.redhat.com/ubi8/nodejs-16-minimal:latest printenv PATH /node_modules/.bin/:/.npm-global/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin In testing on my machine, it seems to be because the HOME variable and the PATH variable are declared in the same ENV action. Separating them resolved this for me, though it seems like it should have worked as expected. Either way, I wanted to report it to see if there was something that I could do to resolve this, or if there was simply an error in how I was using this image. Regards, Jos? R. Gonz?lez Red Hat | Partner Lifecycle Engineering -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkubat at redhat.com Tue Dec 21 14:07:14 2021 From: pkubat at redhat.com (Petr Kubat) Date: Tue, 21 Dec 2021 15:07:14 +0100 Subject: [scl.org] ubi8/nodejs-16-minimal HOME env and PATH In-Reply-To: References: Message-ID: <596f658c-9ceb-efbf-d6cb-56f3f1fc9f58@redhat.com> Hi Jose, thanks for the report! You are correct, the definitions should be in different ENV commands. I created a PR against sclorg repository: https://github.com/sclorg/s2i-nodejs-container/pull/309 Petr On 12/10/21 11:37 PM, Jose Gonzalez wrote: > Hi there! > > I attempted to use the ubi8/nodejs-16-minimal?image > (https://catalog.redhat.com/software/containers/ubi8/nodejs-16-minimal/615aefd53f6014fa45ae1ae2 > ) > and couldn't seem to get the PATH to refer to the appropriate $HOME > location. The result is that the node_modules paths are all relative > to root ("/") instead of relative to the /opt/app-root/src path > > $ docker run -it > registry.access.redhat.com/ubi8/nodejs-16-minimal:latest > > printenv PATH > /node_modules/.bin/:/.npm-global/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > > In testing on my machine, it seems to be because the HOME variable and > the PATH variable are declared in the same ENV action. Separating them > resolved this for me, though it seems like it should have worked as > expected. > > Either way, I wanted to report it to see if there was something that I > could do to resolve this, or if there was simply an error in how I was > using this image. > > Regards, > > Jos? R. Gonz?lez > Red Hat | Partner Lifecycle Engineering > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://listman.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- An HTML attachment was scrubbed... URL: