Open SuperDarius-git opened 3 days ago
2024-11-23 05:19:20+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
FYI 11.5.2 is now EOL, and 11.6.2 is the latest. Probably won't change the issue you are facing.
2024-11-23 05:19:29+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
Note this is just a warning. As it gets to the next output its not stalling here. The memory pressure unavailable just means MariaDB won't respond to approaching OOM conditions by freeing some unused buffers.
2024-11-23 05:19:29+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
I think this is the crux of the problem. The next statement after this is the actual switch:
exec gosu mysql "${BASH_SOURCE[0]}" "$@"
That is its re-executing the same script under the mysql user.
Lets just test a simpler case for your MariaDB service:
command: gosu mysql id -u
ref: command
So this simplified version will confirm its its a problem. Working output would be:
$ podman run --rm mariadb:11.5.2 gosu mysql id -u
999
I suspect the secomp filter of promox is interfering here. I couldn't see a compose option for privileged for a service.
If /var/lib/mysql is initialized then you can use user: mysql
, but maybe this is the same problem as #621.
Unrelated questions on Dockerfile:
Set correct permissions for /tmp directory
RUN chmod 1777 /tmp
This isn't the case already?
RUN chown -R mysql:mysql /var/lib/mysql RUN chmod -R 755 /var/lib/mysql
Its this the default?
Copy custom MySQL configuration file
COPY deploy/my.cnf /etc/mysql/my.cnf
note /etc/mysql/conf.d is the only documented working location https://hub.docker.com/_/mariadb/.
Also command version of the file are parsed so: command: --innodb-buffer-pool-size=20G --innodb-log-file-size=20G
is an option.
@grooverdan - I am so thankful for your reply and answer (and questions) on my issue post, but I am a supershort guy, so everything you just said went straight over my head! - 😂
I am just trying to install or run the different software. Is there something you can suggest me to do? Or direction in any way?
Where should I change the command for testing?
Thank you Darius
Where should I change the command for testing?
As an addition line in the database service.
database:
build:
context: .
dockerfile: Dockerfile.mariadb
restart: "unless-stopped"
command: gosu mysql id -u
environment:
MARIADB_RANDOM_ROOT_PASSWORD: "yes"
MARIADB_INITDB_SKIP_TZINFO: 1
MARIADB_DATABASE: "${DB_MYSQL_NAME}"
MARIADB_USER: "${DB_MYSQL_USER}"
MARIADB_PASSWORD: "${DB_MYSQL_PASSWORD}"
MARIADB_AUTO_UPGRADE: 1
....
This only confirms the problem.
database:
build:
context: .
dockerfile: Dockerfile.mariadb
restart: "unless-stopped"
user: mysql
Might be the workaround once the data is initialized from the first start, if you manage the first start.
Other option is named volumes.
Good day
Let's start at the beginning: I am using a Proxmox server and created an LXC container with Ubuntu 22.04. On that container, I installed Azuracast on with their install Docker script. Everything worked well for very long, then I updated to the latest release and the following happened when updating, installing, and even reinstalling from scratch on a brand new LXC container. One note: The Proxmox server was on version 7 something, which were already not supported anymore. I installed a different Proxmox on a test machine, but this time the latest version 8 something. Everything worked perfectly with the new test machine.
This is the logs for the installation of Azuracast on the version 7 Proxmox LXC container:
Here it just stopped with nothing happened.
I created an issue on the Azruacast Github page: https://github.com/AzuraCast/AzuraCast/issues/7553
I then upgraded the Proxmox server to the latest version 8, but still no fix.
I now am trying to install Avideo on another LXC Ubuntu 24 container. Here is the Docker compose file:
Here is the Dockerfile.mariadb file:
These are the errors on all the databse containers:
Please help me.
Thank you Darius