search

MariaDB / mariadb-docker

Docker Official Image packaging for MariaDB
https://mariadb.org
GNU General Public License v2.0
765 stars 440 forks source link

11.5.2 Entrypoint triggered multiple times #605

Open Simbiat opened 1 month ago

Simbiat commented 1 month ago

It looks like 11.5.2-noble starts entrypoint 3 times at once. Here's what I have in docker logs:

2024-08-16 07:54:00 2024-08-16 04:54:00+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-08-16 07:54:01 2024-08-16  4:54:01 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-08-16 07:54:04 2024-08-16 04:54:04+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-08-16 07:54:04 2024-08-16  4:54:04 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-08-16 07:54:07 2024-08-16 04:54:07+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-08-16 07:54:07 2024-08-16  4:54:07 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-08-16 07:54:00 2024-08-16 04:54:00+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-16 07:54:00 2024-08-16 04:54:00+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-16 07:54:00 2024-08-16 04:54:00+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-16 07:54:01 2024-08-16 04:54:01+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-08-16 07:54:03 2024-08-16 04:54:03+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-16 07:54:04 2024-08-16 04:54:04+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-16 07:54:04 2024-08-16 04:54:04+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-16 07:54:04 2024-08-16 04:54:04+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-08-16 07:54:06 2024-08-16 04:54:06+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-16 07:54:07 2024-08-16 04:54:07+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-16 07:54:07 2024-08-16 04:54:07+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-16 07:54:07 2024-08-16 04:54:07+00:00 [Note] [Entrypoint]: MariaDB upgrade not required

And here's what I have in my log file

2024-08-16  4:54:01 0 [Note] Starting MariaDB 11.5.2-MariaDB-ubu2404 source revision ea75a0b6009b0251e83193cd38c3974e36b65e06 server_uid +4pM6y9U0t2AhkwKrue72/fmrSY= as process 28
2024-08-16  4:54:01 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-08-16  4:54:01 0 [Note] InnoDB: Number of transaction pools: 1
2024-08-16  4:54:01 0 [Note] InnoDB: Using AVX512 instructions
2024-08-16  4:54:01 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-08-16  4:54:01 0 [Note] InnoDB: Using liburing
2024-08-16  4:54:01 0 [Note] InnoDB: Initializing buffer pool, total size = 9.000GiB, chunk size = 144.000MiB
2024-08-16  4:54:01 0 [Note] InnoDB: Completed initialization of buffer pool
2024-08-16  4:54:01 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-08-16  4:54:01 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2024-08-16  4:54:01 0 [ERROR] InnoDB: The error means mariadbd does not have the access rights to the directory.
2024-08-16  4:54:01 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2024-08-16  4:54:01 0 [ERROR] InnoDB: The error means mariadbd does not have the access rights to the directory.
2024-08-16  4:54:01 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2024-08-16  4:54:01 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2024-08-16  4:54:01 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2024-08-16  4:54:01 0 [Note] InnoDB: Starting shutdown...
2024-08-16  4:54:01 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-08-16  4:54:01 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-08-16  4:54:01 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-08-16  4:54:01 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-08-16  4:54:01 0 [ERROR] Aborting
2024-08-16  4:54:04 0 [Note] Starting MariaDB 11.5.2-MariaDB-ubu2404 source revision ea75a0b6009b0251e83193cd38c3974e36b65e06 server_uid +4pM6y9U0t2AhkwKrue72/fmrSY= as process 28
2024-08-16  4:54:04 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-08-16  4:54:04 0 [Note] InnoDB: Number of transaction pools: 1
2024-08-16  4:54:04 0 [Note] InnoDB: Using AVX512 instructions
2024-08-16  4:54:04 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-08-16  4:54:04 0 [Note] InnoDB: Using liburing
2024-08-16  4:54:04 0 [Note] InnoDB: Initializing buffer pool, total size = 9.000GiB, chunk size = 144.000MiB
2024-08-16  4:54:04 0 [Note] InnoDB: Completed initialization of buffer pool
2024-08-16  4:54:05 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-08-16  4:54:05 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2024-08-16  4:54:05 0 [ERROR] InnoDB: The error means mariadbd does not have the access rights to the directory.
2024-08-16  4:54:05 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2024-08-16  4:54:05 0 [ERROR] InnoDB: The error means mariadbd does not have the access rights to the directory.
2024-08-16  4:54:05 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2024-08-16  4:54:05 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2024-08-16  4:54:05 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2024-08-16  4:54:05 0 [Note] InnoDB: Starting shutdown...
2024-08-16  4:54:05 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-08-16  4:54:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-08-16  4:54:05 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-08-16  4:54:05 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-08-16  4:54:05 0 [ERROR] Aborting
2024-08-16  4:54:07 0 [Note] Starting MariaDB 11.5.2-MariaDB-ubu2404 source revision ea75a0b6009b0251e83193cd38c3974e36b65e06 server_uid +4pM6y9U0t2AhkwKrue72/fmrSY= as process 28
2024-08-16  4:54:07 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-08-16  4:54:07 0 [Note] InnoDB: Number of transaction pools: 1
2024-08-16  4:54:07 0 [Note] InnoDB: Using AVX512 instructions
2024-08-16  4:54:07 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-08-16  4:54:07 0 [Note] InnoDB: Using liburing
2024-08-16  4:54:07 0 [Note] InnoDB: Initializing buffer pool, total size = 9.000GiB, chunk size = 144.000MiB
2024-08-16  4:54:07 0 [Note] InnoDB: Completed initialization of buffer pool
2024-08-16  4:54:08 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-08-16  4:54:08 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer
2024-08-16  4:54:09 0 [Note] InnoDB: End of log at LSN=811645479473
2024-08-16  4:54:09 0 [Note] InnoDB: Opened 3 undo tablespaces
2024-08-16  4:54:09 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2024-08-16  4:54:09 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-08-16  4:54:09 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-08-16  4:54:09 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-08-16  4:54:09 0 [Note] InnoDB: log sequence number 811645479473; transaction id 233174687
2024-08-16  4:54:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-08-16  4:54:09 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-08-16  4:54:09 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-08-16  4:54:09 0 [Note] Recovering after a crash using tc.log
2024-08-16  4:54:09 0 [Note] Starting table crash recovery...
2024-08-16  4:54:09 0 [Note] Crash table recovery finished.
2024-08-16  4:54:09 0 [Note] InnoDB: Buffer pool(s) load completed at 240816  4:54:09
2024-08-16  4:54:09 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-08-16  4:54:09 0 [Note] Server socket created on IP: '::'.
2024-08-16  4:54:10 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
2024-08-16  4:54:10 0 [Note] mariadbd: ready for connections.
Version: '11.5.2-MariaDB-ubu2404'  socket: '/run/mysqld/mysqld.sock'  port: 19913  mariadb.org binary distribution

My dockercompose service

  local.simbiat.dev:
    container_name: mariadb
    build:
      context: ./config/mysql
      dockerfile: Dockerfile
    restart: unless-stopped
    environment:
      WEB_SERVER_TEST: ${WEB_SERVER_TEST}
      MARIADB_AUTO_UPGRADE: true
      #Settings for SSL certificates generated by CRON job
      MARIADB_TLS_SETTING_CA_NAME: ${MARIADB_TLS_SETTING_CA_NAME}
      MARIADB_TLS_SETTING_CLIENT_NAME: ${MARIADB_TLS_SETTING_CLIENT_NAME}
      MARIADB_TLS_SETTING_SERVER_NAME: ${MARIADB_TLS_SETTING_SERVER_NAME}
      #Alias in format of "DNS:domain_name[,DNS:domain_name2]". If you do not need an alias use the servername for "domain_name"
      MARIADB_TLS_SETTING_SERVER_ALIAS: ${MARIADB_TLS_SETTING_SERVER_ALIAS}
      #Password for backups created by CRON job
      MARIADB_BACKUP_PASSWORD: ${WEB_SERVER_TEST}
    networks:
      - webserver
    ports:
      - ${MARIADB_PORT}:${MARIADB_PORT}
    volumes:
      - ${MARIADB_DATA_DIR}:/var/lib/mysql:rw
      - ./config/mysql:/etc/mysql/conf.d:ro
      - ${MARIADB_KEYS_DIR}:/usr/local/keys:rw
      - ./logs:/usr/local/logs:rw
      - ${MARIADB_BACKUP_DIR}:/usr/local/backups:rw
      - ./build/DDL:/usr/local/DDL:ro
    security_opt:
      - no-new-privileges=true
    healthcheck:
      test: [ "CMD", "healthcheck.sh", "--defaults-file=/etc/mysql/conf.d/my.cnf", "--connect", "--innodb_initialized", "--innodb_buffer_pool_loaded", "--mariadbupgrade" ]
      start_period: 120s
      interval: 10s
      timeout: 5s
      retries: 3
    #We want to generate keys automatically, and it is also a good idea to regenerate them on each restart
    #We need to ensure that buffer pool file exists, too
    #We need to register cron tasks and start cron service before the endpoint
    command: >
      /bin/sh -c "printenv | grep -v "no_proxy" > /etc/environment &&
                  /etc/mysql/conf.d/cron/ssl.sh &&
                  touch /var/lib/mysql/ib_buffer_pool &&
                  chown mysql:mysql /var/lib/mysql/ib_buffer_pool &&
                  cp /etc/mysql/conf.d/cron/mariadb.cron /etc/cron.d/mariadb.cron &&
                  chmod 0644 /etc/cron.d/mariadb.cron &&
                  crontab /etc/cron.d/mariadb.cron &&
                  cron &&
                  docker-entrypoint.sh mariadbd"

My dockerfile

FROM mariadb:11.5.2-noble

# Need cron, LZ4 compression plugin for MariaDB, and 7zip for backups compression
RUN apt-get -y update&&apt-get -y upgrade&&apt-get -y install cron mariadb-plugin-provider-lz4 7zip&&apt-get -y autoremove

This behavior is not observed on 11.4.3-noble. Number of repeats seem to vary, too: sometimes it's 2, sometimes it's 3. It is possible that container is actually crashing (because MariaDB fails to start), but it's a bit unclear.

grooverdan commented 4 weeks ago

The primary cause appears to be:

2024-08-16  4:54:05 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2024-08-16  4:54:05 0 [ERROR] InnoDB: The error means mariadbd does not have the access rights to the directory.

https://mariadb.com/kb/en/docker-official-image-frequently-asked-questions/#every-mariadb-start-gives-permission-denied-messages

The volume mount of path leave it to the container to resolve the permissions. Despite the container started as root, where it should try to chown the container datadir to user mysql, no-new-privileges might be preventing the transition to the mysql user.

I can't see a reason for 3 restarts. (or special ib_buffer_pool handling).

Simbiat commented 4 weeks ago

Indeed, removing no-new-privileges=true from compose solves this. But why is there no issues with 11.4.3 then?

Logs without the option for reference:

2024-08-19 07:07:31 2024-08-19 04:07:31+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-19 07:07:32 2024-08-19 04:07:32+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-08-19 07:07:32 2024-08-19 04:07:32+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-19 07:07:32 2024-08-19 04:07:32+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
2024-08-19 07:07:32 2024-08-19 04:07:32+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-08-19 07:07:32 2024-08-19  4:07:32 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-08-19  4:07:32 0 [Note] Starting MariaDB 11.5.2-MariaDB-ubu2404 source revision ea75a0b6009b0251e83193cd38c3974e36b65e06 server_uid +4pM6y9U0t2AhkwKrue72/fmrSY= as process 28
2024-08-19  4:07:32 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-08-19  4:07:32 0 [Note] InnoDB: Number of transaction pools: 1
2024-08-19  4:07:32 0 [Note] InnoDB: Using AVX512 instructions
2024-08-19  4:07:32 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-08-19  4:07:32 0 [Note] InnoDB: Using liburing
2024-08-19  4:07:32 0 [Note] InnoDB: Initializing buffer pool, total size = 9.000GiB, chunk size = 144.000MiB
2024-08-19  4:07:33 0 [Note] InnoDB: Completed initialization of buffer pool
2024-08-19  4:07:33 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-08-19  4:07:33 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer
2024-08-19  4:07:34 0 [Note] InnoDB: End of log at LSN=811645509288
2024-08-19  4:07:34 0 [Note] InnoDB: Opened 3 undo tablespaces
2024-08-19  4:07:34 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2024-08-19  4:07:34 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-08-19  4:07:34 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-08-19  4:07:34 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-08-19  4:07:34 0 [Note] InnoDB: log sequence number 811645509288; transaction id 233174741
2024-08-19  4:07:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-08-19  4:07:34 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-08-19  4:07:34 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-08-19  4:07:34 0 [Note] Recovering after a crash using tc.log
2024-08-19  4:07:34 0 [Note] InnoDB: Buffer pool(s) load completed at 240819  4:07:34
2024-08-19  4:07:34 0 [Note] Starting table crash recovery...
2024-08-19  4:07:34 0 [Note] Crash table recovery finished.
2024-08-19  4:07:35 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-08-19  4:07:35 0 [Note] Server socket created on IP: '::'.
2024-08-19  4:07:35 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
2024-08-19  4:07:35 0 [Note] mariadbd: ready for connections.
Version: '11.5.2-MariaDB-ubu2404'  socket: '/run/mysqld/mysqld.sock'  port: 19913  mariadb.org binary distribution

Logs from 11.4.3 with no-new-priviileges:

2024-08-19 07:11:24 2024-08-19 04:11:24+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.3+maria~ubu2404 started.
2024-08-19 07:11:24 2024-08-19 04:11:24+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-08-19 07:11:24 2024-08-19 04:11:24+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.3+maria~ubu2404 started.
2024-08-19 07:11:25 2024-08-19 04:11:25+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2024-08-19 07:11:24 2024-08-19 04:11:24+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-08-19 07:11:25 2024-08-19  4:11:25 0 [Warning] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-08-19  4:11:25 0 [Note] Starting MariaDB 11.4.3-MariaDB-ubu2404 source revision 5ab81ffe0097a22a774957df28c5223cf0201de3 server_uid +4pM6y9U0t2AhkwKrue72/fmrSY= as process 28
2024-08-19  4:11:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-08-19  4:11:25 0 [Note] InnoDB: Number of transaction pools: 1
2024-08-19  4:11:25 0 [Note] InnoDB: Using AVX512 instructions
2024-08-19  4:11:25 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-08-19  4:11:25 0 [Note] InnoDB: Using liburing
2024-08-19  4:11:25 0 [Note] InnoDB: Initializing buffer pool, total size = 9.000GiB, chunk size = 144.000MiB
2024-08-19  4:11:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-08-19  4:11:25 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-08-19  4:11:25 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer
2024-08-19  4:11:27 0 [Note] InnoDB: End of log at LSN=811645509288
2024-08-19  4:11:27 0 [Note] InnoDB: Opened 3 undo tablespaces
2024-08-19  4:11:27 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2024-08-19  4:11:27 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-08-19  4:11:27 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-08-19  4:11:27 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-08-19  4:11:27 0 [Note] InnoDB: log sequence number 811645509288; transaction id 233174741
2024-08-19  4:11:27 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-08-19  4:11:27 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-08-19  4:11:27 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-08-19  4:11:27 0 [Note] Recovering after a crash using tc.log
2024-08-19  4:11:27 0 [Note] InnoDB: Buffer pool(s) load completed at 240819  4:11:27
2024-08-19  4:11:27 0 [Note] Starting table crash recovery...
2024-08-19  4:11:27 0 [Note] Crash table recovery finished.
2024-08-19  4:11:27 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-08-19  4:11:27 0 [Note] Server socket created on IP: '::'.
2024-08-19  4:11:27 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
2024-08-19  4:11:27 0 [Note] mariadbd: ready for connections.
Version: '11.4.3-MariaDB-ubu2404'  socket: '/run/mysqld/mysqld.sock'  port: 19913  mariadb.org binary distribution
Simbiat commented 4 weeks ago

Hm, that's interesting, I went back to 11.5.2 after getting above logs from 11.4.3 on my test environment and... the issue is gone on the rebuilt container 🤔

grooverdan commented 4 weeks ago

Changing ownership was made non-fatal - https://github.com/docker-library/official-images/pull/17344

Healthcheck also slightly reworked (but don't think that plays a part here).

Simbiat commented 4 weeks ago

but I tried updating after that release was merged, so not sure. also not sure what change of ownership would be at play here, too.

Simbiat commented 3 weeks ago

hm, I upgraded PROD and no issue there, but on test it returned once more. I wonder if this is somehow related to my test host being Windows

grooverdan commented 3 weeks ago

Ack, sorry I can't test all host environments. They, by the goals of containers, should result in something identical.

Simbiat commented 3 weeks ago

I am not saying you should 😅 My job here is small - report something abnormal I've noticed and all relevant information that may help solve it, if at all possible. It does not seem to be affecting actual data or the server as a whole, once it's running, so I'd say this is a low priority thing, too.