-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gosu failing under Proxmox 7 LXC #624
Comments
FYI 11.5.2 is now EOL, and 11.6.2 is the latest. Probably won't change the issue you are facing.
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.
I think this is the crux of the problem. The next statement after this is the actual switch:
That is its re-executing the same script under the mysql user. Lets just test a simpler case for your MariaDB service:
ref: command So this simplified version will confirm its its a problem. Working output would be:
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 Unrelated questions on Dockerfile:
This isn't the case already?
Its this the default?
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: |
@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 |
As an addition line in the database service.
This only confirms the problem.
Might be the workaround once the data is initialized from the first start, if you manage the first start. Other option is named volumes. |
@grooverdan - Thank you so much for your reply. I do understand it better, but can not test this yet, because I am having problems with my power at my home lab, it's been off for 48 hours now. I will test this as soon as power comes back on. I just don't want you to think I disappeared. |
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:
AzuraCast/AzuraCast#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
The text was updated successfully, but these errors were encountered: