profile
viewpoint

documize/community 1214

Modern Confluence alternative designed for internal & external docs, built with Golang + EmberJS

pnelson/cli 3

Provides structure for command line applications.

pnelson/flask-passport 3

Flask authorization and authentication helpers.

pnelson/fraction 2

Approximate fractions from floats.

pnelson/cstringex 1

String utility class.

pnelson/archive 0

A collection of Go archive packages.

pnelson/bundix 0

Generates a Nix expression for your Bundler-managed application.

pnelson/cconfig 0

Configuration file parser.

pnelson/cli-reflection 0

Provides structure for command line applications with sub-commands.

issue commentdocker-library/postgres

User and database not created with docker-compose

Please make sure there is no other postgres processes running on the same port you export the container.

foucdeg

comment created time in a day

issue commentdocker-library/postgres

Getting issue when running postgres container on ppc64le

no i checked space is available.

ShubhamKale

comment created time in 3 days

issue commentdocker-library/postgres

Getting issue when running postgres container on ppc64le

I'm (still) not able to reproduce -- is your server perhaps running out of resources such as memory or disk space?

$ docker pull postgres
Using default tag: latest
latest: Pulling from library/postgres
Digest: sha256:839d6212e7aadb9612fd216374279b72f494c9c4ec517b8e98d768ac9dd74a15
Status: Image is up to date for postgres:latest
docker.io/library/postgres:latest

$ docker run -d -e POSTGRES_PASSWORD=Test@db2 -e POSTGRES_USER=testuser -e POSTGRES_DB=testdb -v testDbVolume:/var/lib/postgresql/data -p 54322:5432 postgres
dbe59c1d6f6ededd2a217da6bd595c687c90c5d1f85571fd6b8527e8e3a85c92

$ docker logs dbe59c1d6f6ededd2a217da6bd595c687c90c5d1f85571fd6b8527e8e3a85c92
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/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....2020-11-25 16:26:04.037 UTC [46] LOG:  starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-25 16:26:04.038 UTC [46] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-25 16:26:04.043 UTC [47] LOG:  database system was shut down at 2020-11-25 16:26:03 UTC
2020-11-25 16:26:04.046 UTC [46] LOG:  database system is ready to accept connections
 done
server started
CREATE DATABASE


/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

2020-11-25 16:26:04.279 UTC [46] LOG:  received fast shutdown request
waiting for server to shut down....2020-11-25 16:26:04.280 UTC [46] LOG:  aborting any active transactions
2020-11-25 16:26:04.281 UTC [46] LOG:  background worker "logical replication launcher" (PID 53) exited with exit code 1
2020-11-25 16:26:04.281 UTC [48] LOG:  shutting down
2020-11-25 16:26:04.290 UTC [46] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2020-11-25 16:26:04.418 UTC [1] LOG:  starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-25 16:26:04.418 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2020-11-25 16:26:04.418 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2020-11-25 16:26:04.421 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-25 16:26:04.424 UTC [64] LOG:  database system was shut down at 2020-11-25 16:26:04 UTC
2020-11-25 16:26:04.428 UTC [1] LOG:  database system is ready to accept connections
ShubhamKale

comment created time in 3 days

PR opened docker-library/postgres

Set GID and UID via ENV variables

Add convenient way to set UID and GID of postgres user and group via ENV variables.

In some cases UID/GID 999 is already blocked by another user (for example openmediavault uses 999 as UID for the openmediavault user). This results in postgres docker container using the already existing user.

+29 -15

0 comment

7 changed files

pr created time in 4 days

issue commentdocker-library/postgres

Default POSTGRES_HOST_AUTH_METHOD=md5 value is not applied for localhost connections

Ah I was thinking of mysql which uses a unix socket if the hostname is localhost https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-connection-socket.html You're right Postgres still uses tcp/ip for localhost and 127.0.0.1

If you have further questions you could try asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow. Since these repos aren't really a user-help forum

AnatoliyTishaevTR

comment created time in 4 days

issue closeddocker-library/postgres

Issue with the usage of the image

When I try to use the image I receive odd errors... It happens only when I try to add "volume" (without volumes everything works fine).

The docker-compose.yml file content:

version: '3'
services:

#  strapi:
#    image: strapi/strapi
#    environment:
#      DATABASE_CLIENT: postgres
#      DATABASE_NAME: strapi
#      DATABASE_HOST: postgres
#      DATABASE_PORT: 5432
#      DATABASE_USERNAME: strapi
#      DATABASE_PASSWORD: strapi
#    links:
#      - postgres:postgres
#    volumes:
#      - ./app:/srv/app
#    ports:
#      - '1337:1337'

  postgres:
    image: postgres
    environment:
      POSTGRES_USER: strapi
      POSTGRES_PASSWORD: strapi
    volumes:
      - ./data:/var/lib/postgresql/data
    ports:
      - '5432:5432'

The errors I received:

Creating strapi-proj_postgres_1 ... done Attaching to strapi-proj_postgres_1 postgres_1 | The files belonging to this database system will be owned by user "postgres". postgres_1 | This user must also own the server process. postgres_1 | postgres_1 | The database cluster will be initialized with locale "en_US.utf8". postgres_1 | The default database encoding has accordingly been set to "UTF8". postgres_1 | The default text search configuration will be set to "english". postgres_1 | postgres_1 | Data page checksums are disabled. postgres_1 | postgres_1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok postgres_1 | creating subdirectories ... ok postgres_1 | selecting dynamic shared memory implementation ... posix postgres_1 | selecting default max_connections ... 100 postgres_1 | selecting default shared_buffers ... 128MB postgres_1 | selecting default time zone ... Etc/UTC postgres_1 | creating configuration files ... ok postgres_1 | running bootstrap script ... 2020-11-08 20:52:38.581 UTC [38] FATAL: unexpected data beyond EOF in block 0 of relation base/1/1249 postgres_1 | 2020-11-08 20:52:38.581 UTC [38] HINT: This has been seen to occur with buggy kernels; consider updating your system. postgres_1 | 2020-11-08 20:52:38.581 UTC [38] PANIC: cannot abort transaction 1, it was already committed postgres_1 | Aborted postgres_1 | child process exited with exit code 134 postgres_1 | initdb: removing contents of data directory "/var/lib/postgresql/data" strapi-proj_postgres_1 exited with code 1

Few more things to mention:

  1. OS: MacOS Catalina 10.15.7
  2. When I try to use volume - /tmp/data:/var/lib/postgresql/data everything works fine (but it's not an option since I need to persist the data)
  3. "./data" folder has next permissions: drwxr-xr-x

Maybe someone faced the same issue?

closed time in 4 days

Ddzhenyik

issue commentdocker-library/postgres

Issue with the usage of the image

As implied above, we cannot reproduce, so there's nothing we can do from here without more information.

To continue this diagnosis further, I'd suggest trying a dedicated support forum such as the Docker Community Forums, the Docker Community Slack, or Stack Overflow.

Ddzhenyik

comment created time in 4 days

issue commentdocker-library/postgres

Issue with the usage of the image

up ?

Ddzhenyik

comment created time in 4 days

issue commentdocker-library/postgres

Error FATAL: password authentication failed for user "postgres"

Hello,

I'm having the same error here,

The error occurs when I try to connect from my NodeJS app, but it works fine when I connect from a BeeKeeper Studio client. Of course, I made sure I use the same password in both.

Therefore my thinking goes to this error originating from an invisible character or something similar, not from PostgreSQL itself.

bryanhuntesl

comment created time in 4 days

PR opened alpinelinux/docker-alpine

Execute "docker run" without interactive TTY

Fixes #120 by removing the -it flags for docker run in the preparation step. This should have no negative consequences as the executed image does not require any interaction.

+2 -1

0 comment

1 changed file

pr created time in 4 days

issue openedalpinelinux/docker-alpine

Prepare step fails when no TTY is available

Issue Description: The command ./prepare-branch.sh prepare $VERSION will fail when no TTY is available. This prevents us from building docker-alpine within our GitLab CI/CD.

Cause of the issue: The docker run command within the prepare-branch.sh script uses the flags -it for an interactive TTY.

created time in 4 days

issue commentdocker-library/postgres

Default POSTGRES_HOST_AUTH_METHOD=md5 value is not applied for localhost connections

@wglambert Thank you for clarifications. I didn't know that -h localhost still will use socket and not a TCP/IP connection.

Actually wondering how is then possible to trigger TCP/IP connection via psql from localhost? Documentation says if -h is not specified then "local socket" is used. And I was assuming that otherwise we will not use socket but TCP/IP

$ psql --help

Connection options:
  -h, --host=HOSTNAME      database server host or socket directory (default: "local socket")
AnatoliyTishaevTR

comment created time in 4 days

issue commentdocker-library/postgres

Getting issue when running postgres container on ppc64le

docker run -d -e POSTGRES_PASSWORD=Test@db2 -e POSTGRES_USER=testuser -e POSTGRES_DB=testdb -v testDbVolume:/var/lib/postgresql/data -p 54322:5432 postgres

this command i used

ShubhamKale

comment created time in 4 days

issue commentdocker-library/postgres

Getting issue when running postgres container on ppc64le

I'm not able to reproduce -- is your server perhaps running out of resources such as memory or disk space?

$ docker images postgres:13
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
postgres            13                  ff7c5eb3b0b0        5 days ago          373MB

$ docker run -it --rm --name test -e POSTGRES_PASSWORD=foo postgres:13
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/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....2020-11-23 19:29:33.448 UTC [46] LOG:  starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-23 19:29:33.711 UTC [46] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-23 19:29:33.822 UTC [47] LOG:  database system was shut down at 2020-11-23 19:29:31 UTC
.2020-11-23 19:29:34.658 UTC [46] LOG:  database system is ready to accept connections
 done
server started

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

waiting for server to shut down....2020-11-23 19:29:35.042 UTC [46] LOG:  received fast shutdown request
2020-11-23 19:29:35.087 UTC [46] LOG:  aborting any active transactions
2020-11-23 19:29:35.091 UTC [46] LOG:  background worker "logical replication launcher" (PID 53) exited with exit code 1
2020-11-23 19:29:35.094 UTC [48] LOG:  shutting down
....2020-11-23 19:29:39.643 UTC [46] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2020-11-23 19:29:41.013 UTC [1] LOG:  starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-23 19:29:41.014 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2020-11-23 19:29:41.014 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2020-11-23 19:29:41.615 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-23 19:29:41.733 UTC [55] LOG:  database system was shut down at 2020-11-23 19:29:39 UTC
2020-11-23 19:29:44.308 UTC [1] LOG:  database system is ready to accept connections
ShubhamKale

comment created time in 5 days

issue commentdocker-library/postgres

Default POSTGRES_HOST_AUTH_METHOD=md5 value is not applied for localhost connections

Right, the second entry: host all all 127.0.0.1/32 trust is the first matching line for an ipv4 tcp/ip localhost connection

Doing -h localhost will actually use the unix socket, but the preceding local all all trust entry marks that connection method as trusted also

So then the host all all all md5 entry matches everything that's not unix socket or 127.0.0.1/32

POSTGRES_HOST_AUTH_METHOD was added from the discussion in https://github.com/docker-library/postgres/issues/580

Also https://github.com/docker-library/postgres/issues/580#issuecomment-498390248

localhost doesn't mean anything in a Docker context. If you're running your database with localhost being the only thing accessible inside Docker, you might as well not be running it at all (since localhost is only accessible from directly within the PostgreSQL container itself).

AnatoliyTishaevTR

comment created time in 5 days

issue commentalpinelinux/docker-alpine

apk errors with latest (minirootfs-20200917) 32bit arm images

Replacing the package manually is may not a god idea. Other package which link again libseccomp2 could break. Raspbian does not support backports, so this is not a option. I think I will switch my host OS to alpine. I have already planned this, but not done it yet.

minusdelta

comment created time in 5 days

issue commentdocker-library/postgres

Getting issue when running postgres container on ppc64le

duplicate issue

ShubhamKale

comment created time in 5 days

issue closeddocker-library/postgres

Getting issue when running postgres container on ppc64le

Below are logs when tried to run postgres image on Linux PPC machine.

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/postgresql/data ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Etc/UTC creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok initdb: warning: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. syncing data to disk ... ok Success. You can now start the database server using: pg_ctl -D /var/lib/postgresql/data -l logfile start waiting for server to start....2020-11-23 04:42:58.848 UTC [45] LOG: starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit 2020-11-23 04:42:58.852 UTC [45] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-11-23 04:42:58.871 UTC [46] LOG: database system was shut down at 2020-11-23 04:42:55 UTC 2020-11-23 04:42:58.882 UTC [45] LOG: database system is ready to accept connections done server started 2020-11-23 04:42:59.150 UTC [47] PANIC: could not flush dirty data: Operation not permitted 2020-11-23 04:43:00.006 UTC [45] LOG: checkpointer process (PID 47) was terminated by signal 6: Aborted 2020-11-23 04:43:00.006 UTC [45] LOG: terminating any other active server processes 2020-11-23 04:43:00.006 UTC [50] WARNING: terminating connection because of crash of another server process 2020-11-23 04:43:00.006 UTC [50] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2020-11-23 04:43:00.006 UTC [50] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2020-11-23 04:43:00.013 UTC [61] WARNING: terminating connection because of crash of another server process 2020-11-23 04:43:00.013 UTC [61] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2020-11-23 04:43:00.013 UTC [61] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2020-11-23 04:43:00.016 UTC [45] LOG: all server processes terminated; reinitializing WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. connection to server was lost

closed time in 5 days

ShubhamKale

issue openeddocker-library/postgres

Getting issue when running postgres container on ppc64le

Below are logs when tried to run postgres image on Linux PPC machine.

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/postgresql/data ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Etc/UTC creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok initdb: warning: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. syncing data to disk ... ok Success. You can now start the database server using: pg_ctl -D /var/lib/postgresql/data -l logfile start waiting for server to start....2020-11-23 04:42:58.848 UTC [45] LOG: starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit 2020-11-23 04:42:58.852 UTC [45] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-11-23 04:42:58.871 UTC [46] LOG: database system was shut down at 2020-11-23 04:42:55 UTC 2020-11-23 04:42:58.882 UTC [45] LOG: database system is ready to accept connections done server started 2020-11-23 04:42:59.150 UTC [47] PANIC: could not flush dirty data: Operation not permitted 2020-11-23 04:43:00.006 UTC [45] LOG: checkpointer process (PID 47) was terminated by signal 6: Aborted 2020-11-23 04:43:00.006 UTC [45] LOG: terminating any other active server processes 2020-11-23 04:43:00.006 UTC [50] WARNING: terminating connection because of crash of another server process 2020-11-23 04:43:00.006 UTC [50] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2020-11-23 04:43:00.006 UTC [50] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2020-11-23 04:43:00.013 UTC [61] WARNING: terminating connection because of crash of another server process 2020-11-23 04:43:00.013 UTC [61] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2020-11-23 04:43:00.013 UTC [61] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2020-11-23 04:43:00.016 UTC [45] LOG: all server processes terminated; reinitializing WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. connection to server was lost

created time in 5 days

issue openeddocker-library/postgres

Getting issue when running postgres container on ppc64le

Below are logs when tried to run postgres image on Linux PPC machine.

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/postgresql/data ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting default time zone ... Etc/UTC creating configuration files ... ok running bootstrap script ... ok performing post-bootstrap initialization ... ok initdb: warning: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. syncing data to disk ... ok Success. You can now start the database server using: pg_ctl -D /var/lib/postgresql/data -l logfile start waiting for server to start....2020-11-23 04:42:58.848 UTC [45] LOG: starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit 2020-11-23 04:42:58.852 UTC [45] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-11-23 04:42:58.871 UTC [46] LOG: database system was shut down at 2020-11-23 04:42:55 UTC 2020-11-23 04:42:58.882 UTC [45] LOG: database system is ready to accept connections done server started 2020-11-23 04:42:59.150 UTC [47] PANIC: could not flush dirty data: Operation not permitted 2020-11-23 04:43:00.006 UTC [45] LOG: checkpointer process (PID 47) was terminated by signal 6: Aborted 2020-11-23 04:43:00.006 UTC [45] LOG: terminating any other active server processes 2020-11-23 04:43:00.006 UTC [50] WARNING: terminating connection because of crash of another server process 2020-11-23 04:43:00.006 UTC [50] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2020-11-23 04:43:00.006 UTC [50] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2020-11-23 04:43:00.013 UTC [61] WARNING: terminating connection because of crash of another server process 2020-11-23 04:43:00.013 UTC [61] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2020-11-23 04:43:00.013 UTC [61] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2020-11-23 04:43:00.016 UTC [45] LOG: all server processes terminated; reinitializing WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. connection to server was lost

created time in 5 days

issue commentalpinelinux/docker-alpine

tzdata work wrong in America/Santiago since alpine:3.9

Now fixed and available on Alpine stable 3.12 (2020c-r1).

inyerade

comment created time in 6 days

issue openeddocker-library/postgres

Default POSTGRES_HOST_AUTH_METHOD=md5 value is not applied for localhost connections

Description on docker image

POSTGRES_HOST_AUTH_METHOD This optional variable can be used to control the auth-method for host connections for all databases, all users, and all addresses. If unspecified then md5 password authentication is used. On an uninitialized database, this will populate pg_hba.conf via this approximate line:

echo "host all all all $POSTGRES_HOST_AUTH_METHOD" >> pg_hba.conf

Yes, this is happens and at the bottom of pg_hba.conf there is a line host all all all md5 is present. The problem is that we still have standard row above

# IPv4 local connections:
host    all             all             127.0.0.1/32            trust

And because it is above it gets applied first for connections from localhost. And it does allow to login without any passwod specified. Postgres official docs:

The first record with a matching connection type, client address, requested database, and user name is used to perform authentication.

Is this overlooked or IPv4 local connections aren't considered as a "host" ones?

psql -h localhost postgres postgres

created time in 6 days

issue openedalpinelinux/docker-alpine

run alpine and cpu lockup

env:

root@node-4:~# uname -a 
Linux node-4 4.4.131-20190726.kylin.server-generic #kylin SMP Tue Jul 30 16:44:09 CST 2019 aarch64 aarch64 aarch64 GNU/Linux

root@node-4:~# docker version
Client: Docker Engine - Community
 Version:           19.03.9
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        9d98839
 Built:             Fri May 15 00:25:37 2020
 OS/Arch:           linux/arm64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.9
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       9d98839
  Built:            Fri May 15 00:24:11 2020
  OS/Arch:          linux/arm64
  Experimental:     true
 containerd:
  Version:          1.3.7
  GitCommit:        8fba4e9a7d01810a393d5d25a3621dc101981175
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

run the command docker run --rm -it arm64v8/alpine:3.12 sh and then ,

0,13055,786664246336,-;NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [sh:42014]
4,13056,786664253527,c;Modules linked in: xt_REDIRECT nf_nat_redirect xt_tcpudp xt_owner xt_set xt_multiport iptable_raw ip_set_hash_ip ip_set_hash_net ipip tunnel4 ip_tunnel veth ip_set_bitmap_port ip_set_hash_ipportnet ip_set_hash_ipport ip_set_hash_ipportip ip_set dummy ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables iptable_mangle xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay joydev igb ixgbe vxlan ip6_udp_tunnel udp_tunnel mdio shpchp dms5013a crc32_arm64 sunrpc autofs4
4,13057,786664253592,+; megaraid_sas
4,13058,786664253595,-;
4,13059,786664253599,-;CPU: 34 PID: 42014 Comm: sh Tainted: G             L  4.4.131-20190726.kylin.server-generic #kylin
4,13060,786664253602,-;Hardware name: GreatWall \xe6\x5cx93\x5cx8e\xe5\xa4\xa9DF720/N/A, BIOS 601FBE23 Dec  3 2019
4,13061,786664253604,-;task: ffff80835f0ae140 ti: ffff808350c48000 task.ti: ffff808350c48000
4,13062,786664253611,-;PC is at _raw_spin_unlock_irqrestore+0x2c/0x38
4,13063,786664253616,-;LR is at __wake_up+0x58/0x68
4,13064,786664253618,-;pc : [<ffff800000a150fc>] lr : [<ffff800000107018>] pstate: 60000145
4,13065,786664253619,-;sp : ffff808350c4bc00
4,13066,786664253621,-;x29: ffff808350c4bc00 x28: ffff84834e2e0800 
4,13067,786664253624,-;x27: ffff8000004db870 x26: ffff808350c48000 
4,13068,786664253627,-;x25: 0000000000000000 x24: 0000000000000000 
4,13069,786664253630,-;x23: ffff84834864b0c0 x22: 0000000000000004 
4,13070,786664253633,-;x21: 0000000000000001 x20: ffff84834e2e0a30 
4,13071,786664253635,-;x19: 0000000000000140 x18: 2000000000000000 
4,13072,786664253638,-;x17: 0000ffff7921d540 x16: ffff80000024ced8 
4,13073,786664253641,-;x15: 000000000d39ad3d x14: 0000ffff79277f50 
4,13074,786664253643,-;x13: 0000000000000018 x12: 000000000d39ad3c 
4,13075,786664253646,-;x11: 00000000ffffffff x10: ffff808350c48000 
4,13076,786664253649,-;x9 : 000000007fff0000 x8 : 0001000000000000 
4,13077,786664253651,-;x7 : 0000000000000001 x6 : ffff84834d289400 
4,13078,786664253654,-;x5 : dead000000000100 x4 : 0000000000000004 
4,13079,786664253656,-;x3 : 0000000000000000 x2 : 0000000000000001 
4,13080,786664253659,-;x1 : 0000000000000140 x0 : 0000000000007ac6 
4,13081,786664253661,-;
0,13082,786692246335,-;NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [sh:42014]
4,13083,786692253523,c;Modules linked in: xt_REDIRECT nf_nat_redirect xt_tcpudp xt_owner xt_set xt_multiport iptable_raw ip_set_hash_ip ip_set_hash_net ipip tunnel4 ip_tunnel veth ip_set_bitmap_port ip_set_hash_ipportnet ip_set_hash_ipport ip_set_hash_ipportip ip_set dummy ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables iptable_mangle xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay joydev igb ixgbe vxlan ip6_udp_tunnel udp_tunnel mdio shpchp dms5013a crc32_arm64 sunrpc autofs4
4,13084,786692253589,+; megaraid_sas
4,13085,786692253591,-;
4,13086,786692253596,-;CPU: 34 PID: 42014 Comm: sh Tainted: G             L  4.4.131-20190726.kylin.server-generic #kylin
4,13087,786692253598,-;Hardware name: GreatWall \xe6\x5cx93\x5cx8e\xe5\xa4\xa9DF720/N/A, BIOS 601FBE23 Dec  3 2019
4,13088,786692253601,-;task: ffff80835f0ae140 ti: ffff808350c48000 task.ti: ffff808350c48000
4,13089,786692253608,-;PC is at _raw_spin_unlock_irqrestore+0x2c/0x38
4,13090,786692253613,-;LR is at add_wait_queue+0x58/0x68
4,13091,786692253615,-;pc : [<ffff800000a150fc>] lr : [<ffff800000106e48>] pstate: 60000145
4,13092,786692253617,-;sp : ffff808350c4bb80
4,13093,786692253619,-;x29: ffff808350c4bb80 x28: ffff84834e2e0800 
4,13094,786692253622,-;x27: ffff8000004db870 x26: ffff84834e2e08d8 
4,13095,786692253625,-;x25: ffff878347729300 x24: 0000000000000000 
4,13096,786692253627,-;x23: ffff84834864b0c0 x22: ffff878347729300 
4,13097,786692253630,-;x21: ffff808350c4bc60 x20: ffff84834e2e0a30 
4,13098,786692253633,-;x19: 0000000000000140 x18: 2000000000000000 
4,13099,786692253636,-;x17: 0000ffff7921d540 x16: ffff80000024ced8 
4,13100,786692253638,-;x15: 000000000d39ad3d x14: 0000ffff79277f50 
4,13101,786692253641,-;x13: 0000000000000018 x12: 000000000d39ad3c 
4,13102,786692253644,-;x11: 00000000ffffffff x10: ffff808350c48000 
4,13103,786692253646,-;x9 : 000000007fff0000 x8 : 0001000000000000 
4,13104,786692253649,-;x7 : 0000000000000001 x6 : ffff84834d289400 
4,13105,786692253651,-;x5 : ffff84834d289400 x4 : 0001000000000000 
4,13106,786692253654,-;x3 : ffff84834e2e0a38 x2 : ffff84834e2e0a38 
4,13107,786692253657,-;x1 : 0000000000000140 x0 : 000000000000673b 
4,13108,786692253659,-;
3,13109,786699996336,-;INFO: rcu_sched self-detected stall on CPU
3,13110,786700001552,-;\x0934-...: (5999 ticks this GP) idle=893/140000000000001/0 softirq=13250105/13250105 fqs=5775 
3,13111,786700011070,-;\x09 (t=6001 jiffies g=36719561 c=36719560 q=83188)
3,13112,786700016328,-;INFO: rcu_sched detected stalls on CPUs/tasks:
3,13113,786700016336,-;\x0934-...: (5999 ticks this GP) idle=893/140000000000001/0 softirq=13250105/13250105 fqs=5775 
3,13114,786700016386,-;\x09(detected by 7, t=6002 jiffies, g=36719561, c=36719560, q=83188)
6,13115,786700016387,-;Task dump for CPU 34:
6,13116,786700016391,-;sh              R  running task        0 42014  41994 0x00000806
0,13117,786700016392,-;Call trace:
4,13118,786700016398,-;[<ffff8000000861c4>] __switch_to+0xa4/0xb8
4,13119,786700016400,-;[<0002cb7fdb10b980>] 0x2cb7fdb10b980
6,13120,786700041564,-;Task dump for CPU 34:
6,13121,786700041566,-;sh              R  running task        0 42014  41994 0x00000806
0,13122,786700041570,-;Call trace:
4,13123,786700044091,-;[<ffff8000000897f8>] dump_backtrace+0x0/0x178
4,13124,786700044094,-;[<ffff800000089b1c>] show_stack+0x24/0x30
4,13125,786700044099,-;[<ffff8000001cbcb4>] sched_show_task+0xd0/0xdc
4,13126,786700044102,-;[<ffff8000001cc2c8>] dump_cpu_task+0x48/0x54
4,13127,786700044104,-;[<ffff8000001cce48>] rcu_dump_cpu_stacks+0x98/0xb4
4,13128,786700044107,-;[<ffff8000001280d8>] rcu_check_callbacks+0x758/0x8b8
4,13129,786700044110,-;[<ffff80000012da8c>] update_process_times+0x44/0x90
4,13130,786700044114,-;[<ffff80000013ec90>] tick_sched_handle.isra.0+0x38/0x78
4,13131,786700044116,-;[<ffff80000013ed1c>] tick_sched_timer+0x4c/0x90
4,13132,786700044119,-;[<ffff80000012e458>] __hrtimer_run_queues+0x148/0x2c0
4,13133,786700044121,-;[<ffff80000012ecc0>] hrtimer_interrupt+0xa0/0x1d0
4,13134,786700044126,-;[<ffff80000089ba24>] arch_timer_handler_phys+0x3c/0x50
4,13135,786700044128,-;[<ffff80000011b85c>] handle_percpu_devid_irq+0x9c/0x228
4,13136,786700044132,-;[<ffff800000116d1c>] generic_handle_irq+0x34/0x50
4,13137,786700044134,-;[<ffff80000011706c>] __handle_domain_irq+0x6c/0xc0
4,13138,786700044137,-;[<ffff800000081c88>] gic_handle_irq+0x98/0x194
4,13139,786700044139,-;Exception stack(0xffff808350c4baa0 to 0xffff808350c4bbc0)
4,13140,786700044142,-;baa0: 0000000000000140 ffff84834e2e0a30 ffff808350c4bc00 ffff800000a150fc
4,13141,786700044145,-;bac0: 0000000060000145 0000000000000000 0000000000000000 ffff808350c48000
4,13142,786700044147,-;bae0: 000000000000d0d8 0000000000000140 0000000000000001 0000000000000000
4,13143,786700044150,-;bb00: 0000000000000004 dead000000000100 ffff84834d289400 0000000000000001
4,13144,786700044152,-;bb20: 0001000000000000 000000007fff0000 ffff808350c48000 00000000ffffffff
4,13145,786700044154,-;bb40: 000000000d39ad3c 0000000000000018 0000ffff79277f50 000000000d39ad3d
4,13146,786700044157,-;bb60: ffff80000024ced8 0000ffff7921d540 2000000000000000 0000000000000140
4,13147,786700044159,-;bb80: ffff84834e2e0a30 0000000000000001 0000000000000004 ffff84834864b0c0
4,13148,786700044161,-;bba0: 0000000000000000 0000000000000000 ffff808350c48000 ffff8000004db870
4,13149,786700044164,-;[<ffff800000084da8>] el1_irq+0x68/0xc0
4,13150,786700044167,-;[<ffff800000107018>] __wake_up+0x58/0x68
4,13151,786700044172,-;[<ffff8000004d5404>] tty_write_unlock+0x34/0x40
4,13152,786700044174,-;[<ffff8000004d7910>] tty_write+0x190/0x268
4,13153,786700044178,-;[<ffff80000024af04>] do_loop_readv_writev.part.0+0x84/0xb8
4,13154,786700044180,-;[<ffff80000024b7ac>] do_readv_writev+0x1dc/0x270
4,13155,786700044183,-;[<ffff80000024bb18>] vfs_writev+0x58/0x80
4,13156,786700044185,-;[<ffff80000024bba0>] do_writev+0x60/0xf0
4,13157,786700044188,-;[<ffff80000024cf10>] SyS_writev+0x38/0x48
4,13158,786700044191,-;[<ffff8000000854e0>] __sys_trace_return+0x0/0x4
0,13159,786724246336,-;NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [sh:42014]
4,13160,786724253525,c;Modules linked in: xt_REDIRECT nf_nat_redirect xt_tcpudp xt_owner xt_set xt_multiport iptable_raw ip_set_hash_ip ip_set_hash_net ipip tunnel4 ip_tunnel veth ip_set_bitmap_port ip_set_hash_ipportnet ip_set_hash_ipport ip_set_hash_ipportip ip_set dummy ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables iptable_mangle xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay joydev igb ixgbe vxlan ip6_udp_tunnel udp_tunnel mdio shpchp dms5013a crc32_arm64 sunrpc autofs4
4,13161,786724253591,+; megaraid_sas
4,13162,786724253593,-;
4,13163,786724253597,-;CPU: 34 PID: 42014 Comm: sh Tainted: G             L  4.4.131-20190726.kylin.server-generic #kylin
4,13164,786724253599,-;Hardware name: GreatWall \xe6\x5cx93\x5cx8e\xe5\xa4\xa9DF720/N/A, BIOS 601FBE23 Dec  3 2019
4,13165,786724253602,-;task: ffff80835f0ae140 ti: ffff808350c48000 task.ti: ffff808350c48000
4,13166,786724253609,-;PC is at _raw_spin_lock_irqsave+0x1c/0x60
4,13167,786724253614,-;LR is at remove_wait_queue+0x24/0x60
4,13168,786724253616,-;pc : [<ffff800000a15034>] lr : [<ffff800000106ee4>] pstate: 20000145
4,13169,786724253618,-;sp : ffff808350c4bb90
4,13170,786724253619,-;x29: ffff808350c4bb90 x28: ffff84834e2e0800 
4,13171,786724253623,-;x27: ffff8000004db870 x26: ffff84834e2e08d8 
4,13172,786724253626,-;x25: ffff878347729300 x24: ffff800000a7b488 
4,13173,786724253628,-;x23: 0000000000000000 x22: 0000000000000000 
4,13174,786724253631,-;x21: ffff84834d289400 x20: ffff84834e2e0a30 
4,13175,786724253634,-;x19: ffff84834e2e0a30 x18: 2000000000000000 
4,13176,786724253636,-;x17: 0000ffff7921d540 x16: ffff80000024ced8 
4,13177,786724253639,-;x15: 000000000d39ad3d x14: 0000ffff79277f50 
4,13178,786724253642,-;x13: 0000000000000018 x12: 000000000d39ad3c 
4,13179,786724253644,-;x11: 00000000ffffffff x10: ffff808350c48000 
4,13180,786724253647,-;x9 : 000000007fff0000 x8 : 0001000000000000 
4,13181,786724253650,-;x7 : 0000000000000001 x6 : ffff84834d289400 
4,13182,786724253652,-;x5 : ffff84834d289400 x4 : 0001000000000000 
4,13183,786724253655,-;x3 : ffff84834e2e0a38 x2 : ffff84834d289400 
4,13184,786724253657,-;x1 : ffff808350c4bc48 x0 : 0000000000000140 
4,13185,786724253660,-;
0,13186,786752246332,-;NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [sh:42014]
4,13187,786752253522,c;Modules linked in: xt_REDIRECT nf_nat_redirect xt_tcpudp xt_owner xt_set xt_multiport iptable_raw ip_set_hash_ip ip_set_hash_net ipip tunnel4 ip_tunnel veth ip_set_bitmap_port ip_set_hash_ipportnet ip_set_hash_ipport ip_set_hash_ipportip ip_set dummy ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables iptable_mangle xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay joydev igb ixgbe vxlan ip6_udp_tunnel udp_tunnel mdio shpchp dms5013a crc32_arm64 sunrpc autofs4
4,13188,786752253589,+; megaraid_sas
4,13189,786752253590,-;
4,13190,786752253595,-;CPU: 34 PID: 42014 Comm: sh Tainted: G             L  4.4.131-20190726.kylin.server-generic #kylin
4,13191,786752253597,-;Hardware name: GreatWall \xe6\x5cx93\x5cx8e\xe5\xa4\xa9DF720/N/A, BIOS 601FBE23 Dec  3 2019
4,13192,786752253600,-;task: ffff80835f0ae140 ti: ffff808350c48000 task.ti: ffff808350c48000
4,13193,786752253608,-;PC is at ldsem_up_read+0x30/0x60
4,13194,786752253611,-;LR is at tty_ldisc_deref+0x24/0x30
4,13195,786752253613,-;pc : [<ffff8000004e22a0>] lr : [<ffff8000004df924>] pstate: 60000145
4,13196,786752253614,-;sp : ffff808350c4bc30
4,13197,786752253616,-;x29: ffff808350c4bc30 x28: ffff84834e2e0800 
4,13198,786752253620,-;x27: ffff8000004db870 x26: 0000000000000042 
4,13199,786752253623,-;x25: 0000000000000120 x24: 0000000000000000 
4,13200,786752253625,-;x23: ffff84834864b0c0 x22: ffff878347729300 
4,13201,786752253628,-;x21: 0000ffff792789f7 x20: 0000000000000000 
4,13202,786752253631,-;x19: ffff84834e2e0828 x18: 2000000000000000 
4,13203,786752253633,-;x17: 0000ffff7921d540 x16: ffff80000024ced8 
4,13204,786752253636,-;x15: 000000000d39ad3d x14: 0000ffff79277f50 
4,13205,786752253638,-;x13: 0000000000000018 x12: 000000000d39ad3c 
4,13206,786752253641,-;x11: 00000000ffffffff x10: ffff808350c48000 
4,13207,786752253643,-;x9 : 000000007fff0000 x8 : 0001000000000000 
4,13208,786752253646,-;x7 : 0000000000000001 x6 : ffff84834d289400 
4,13209,786752253649,-;x5 : dead000000000100 x4 : 0000000000000004 
4,13210,786752253651,-;x3 : 0000000000000000 x2 : 0000000000000000 
4,13211,786752253654,-;x1 : 0000000000000000 x0 : ffffffffffffffff 
4,13212,786752253656,-;
0,13213,786780246331,-;NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [sh:42014]
4,13214,786780253520,c;Modules linked in: xt_REDIRECT nf_nat_redirect xt_tcpudp xt_owner xt_set xt_multiport iptable_raw ip_set_hash_ip ip_set_hash_net ipip tunnel4 ip_tunnel veth ip_set_bitmap_port ip_set_hash_ipportnet ip_set_hash_ipport ip_set_hash_ipportip ip_set dummy ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables iptable_mangle xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache overlay joydev igb ixgbe vxlan ip6_udp_tunnel udp_tunnel mdio shpchp dms5013a crc32_arm64 sunrpc autofs4
4,13215,786780253586,+; megaraid_sas
4,13216,786780253588,-;
4,13217,786780253591,-;CPU: 34 PID: 42014 Comm: sh Tainted: G             L  4.4.131-20190726.kylin.server-generic #kylin
4,13218,786780253594,-;Hardware name: GreatWall \xe6\x5cx93\x5cx8e\xe5\xa4\xa9DF720/N/A, BIOS 601FBE23 Dec  3 2019
4,13219,786780253597,-;task: ffff80835f0ae140 ti: ffff808350c48000 task.ti: ffff808350c48000
4,13220,786780253603,-;PC is at down_read+0x2c/0x58
4,13221,786780253606,-;LR is at n_tty_write+0x9c/0x460
4,13222,786780253609,-;pc : [<ffff800000a13784>] lr : [<ffff8000004db90c>] pstate: 80000145
4,13223,786780253610,-;sp : ffff808350c4bbb0
4,13224,786780253612,-;x29: ffff808350c4bbb0 x28: ffff84834e2e0800 
4,13225,786780253615,-;x27: ffff8000004db870 x26: ffff84834e2e08d8 
4,13226,786780253618,-;x25: ffff878347729300 x24: 0000000000000000 
4,13227,786780253621,-;x23: ffff84834864b0c0 x22: ffff878347729300 
4,13228,786780253624,-;x21: ffff84834e2e0a30 x20: 0000000000000000 
4,13229,786780253626,-;x19: ffff84834e2e08d8 x18: 2000000000000000 
4,13230,786780253629,-;x17: 0000ffff7921d540 x16: ffff80000024ced8 
4,13231,786780253632,-;x15: 000000000d39ad3d x14: 0000ffff79277f50 
4,13232,786780253634,-;x13: 0000000000000018 x12: 000000000d39ad3c 
4,13233,786780253637,-;x11: 00000000ffffffff x10: ffff808350c48000 
4,13234,786780253639,-;x9 : 000000007fff0000 x8 : 0001000000000000 
4,13235,786780253642,-;x7 : 0000000000000001 x6 : ffff84834d289400 
4,13236,786780253645,-;x5 : ffff84834d289400 x4 : 0001000000000000 
4,13237,786780253647,-;x3 : ffff80835f0ae140 x2 : 0000000000008a30 
4,13238,786780253650,-;x1 : 0000000000000000 x0 : 0000000000000001 
4,13239,786780253652,-;
6,13240,786804718407,-;docker0: port 1(veth71f29ad) entered disabled state
6,13241,786804718628,-;vethb794498: renamed from eth0
6,13242,786804920203,-;docker0: port 1(veth71f29ad) entered disabled state
6,13243,786804941153,-;device veth71f29ad left promiscuous mode
6,13244,786804941159,-;docker0: port 1(veth71f29ad) entered disabled state

root@node-4:~# top 

top - 14:15:37 up 9 days,  2:23,  4 users,  load average: 3.50, 2.04, 1.99
Tasks: 724 total,   6 running, 718 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.9 us,  0.5 sy,  0.0 ni, 98.5 id,  0.1 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem : 26587347+total, 21568915+free, 10836992 used, 39347328 buff/cache
KiB Swap:        0 total,        0 free,        0 used. 21257120+avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                                                 
50269 root      20   0    2048     64      0 R 100.0  0.0   0:14.95 sh          

cpu soft lockup

created time in 6 days

issue commentalpinelinux/docker-alpine

apk errors with latest (minirootfs-20200917) 32bit arm images

I have the same issue with the alpine:edge docker image on my Raspberry Pi 2 (armv7).

Does someone known a workaround? My host (Debian) has only libseccomp2 2.3.3.

I downloaded deb package and installed manually.

minusdelta

comment created time in 6 days

issue closeddocker-library/postgres

pg_basebackup on init

Hi,

I would like to create an initial backup during container initialization using this command:

pg_basebackup -h localhost -p 5432 -U $POSTGRES_USER -D /tmp/base_backup -Ft -z -Xs -P

Giving this:

/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/30-init-backup.sh

pg_basebackup: error: could not connect to server: could not connect to server: Connection refused

	Is the server running on host "localhost" (127.0.0.1) and accepting

	TCP/IP connections on port 5432?

could not connect to server: Cannot assign requested address

	Is the server running on host "localhost" (::1) and accepting

	TCP/IP connections on port 5432?

The same command after init gives me the expecting behavior.

Any idea ?

By advance, thank you.

closed time in 7 days

Loxeno

issue commentdocker-library/postgres

pg_basebackup on init

Solved :

pg_basebackup -U $POSTGRES_USER -D /tmp/base_backup -Ft -z -Xs -P

Loxeno

comment created time in 7 days

issue openeddocker-library/postgres

pg_basebackup on init

Hi,

I would like to create an initial backup during container initialization using this command:

pg_basebackup -h localhost -p 5432 -U $POSTGRES_USER -D /tmp/base_backup -Ft -z -Xs -P

Giving this:

/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/30-init-backup.sh

pg_basebackup: error: could not connect to server: could not connect to server: Connection refused

	Is the server running on host "localhost" (127.0.0.1) and accepting

	TCP/IP connections on port 5432?

could not connect to server: Cannot assign requested address

	Is the server running on host "localhost" (::1) and accepting

	TCP/IP connections on port 5432?

The same command after init gives me the expecting behavior.

Any idea ?

By advance, thank you.

created time in 7 days

issue closeddocker-library/postgres

Trying to find old postgres:9.6 image

Hi, i am trying to locate a postgres:9.6 image that i pulled around July 2019

sha256:edb112fd27660755021fa7d373f968e4f6346ccac1ecfce18a1c79f4c2cd0560

ID: edb112fd2766

It does not show up in any of the searches... I'll greatly appreciate any help.

Thanks!!!

closed time in 7 days

nycalex

issue commentdocker-library/postgres

Trying to find old postgres:9.6 image

Looks like https://github.com/docker-library/repo-info/blob/f425592731cbd386079ee1005757419c282da65c/repos/postgres/remote/9.6.md is probably what you're after.

In the future, these sorts of questions/requests would be more appropriately posted to the Docker Community Forums, the Docker Community Slack, or Stack Overflow.

nycalex

comment created time in 7 days

issue openeddocker-library/postgres

Trying to find old postgres:9.6 image

Hi, i am trying to locate a postgres:9.6 image that i pulled around July 2019

sha256:edb112fd27660755021fa7d373f968e4f6346ccac1ecfce18a1c79f4c2cd0560

ID: edb112fd2766

It does not show up in any of the searches... I'll greatly appreciate any help.

Thanks!!!

created time in 7 days

more