Skip to content
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

Issue - Installing brand new SnipeIT on Docker - MariaDB Issues #16267

Open
leandrobelite opened this issue Feb 18, 2025 · 7 comments
Open

Issue - Installing brand new SnipeIT on Docker - MariaDB Issues #16267

leandrobelite opened this issue Feb 18, 2025 · 7 comments
Labels
docker ❓ not sure if bug This issue has not been confirmed as a bug yet

Comments

@leandrobelite
Copy link

Issue Description

Trying to install a new SnipeIT on the latest version 7.1.16 with MariaDB version 11.5.2 (Default on docker-compose YAML file)

Error received

When trying to get the APP_KEY for the first time or even running "docker compose up" I get the following:

db-1   | 2025-02-18 13:56:49+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.5.2+maria~ubu2404 started.
db-1   | 2025-02-18 13:56:49+00:00 [ERROR] [Entrypoint]: mariadbd failed while attempting to check config
db-1   |        command was: mariadbd --verbose --help
db-1   |        Can't initialize timers

If I modify the docker-compose.yml file and update the mariadb image with another version, let´s say 10.8.2 it goes ahead but it fails because of Health Checks.

Is there any known issue related with that MariaDB version?

Thanks in advance!

Copy link

welcome bot commented Feb 18, 2025

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented Feb 18, 2025

None that I'm aware of. @uberbrady any ideas?

@uberbrady
Copy link
Collaborator

Uhm, wow - no, that's kinda weird. That 'failed to initialize timers' thing feels pretty systems-ey, down in the guts of things. Is this running 'rootless' or something? Or on something other than conventional docker, like podman? Can you spin up a MariaDB container on its own, outside of the context of the docker-compose file?

@snipe
Copy link
Owner

snipe commented Feb 18, 2025

Possibly related? #11978

@snipe snipe added ❓ not sure if bug This issue has not been confirmed as a bug yet docker labels Feb 18, 2025
@leandrobelite
Copy link
Author

Hey @snipe and @uberbrady,

Thanks for the fast response.

Just tried what you suggested ramping up a new mariadb with that same version I am having issues nad the same happened. This is just regular docker installed in Rancher OS (Maybe this is the issue?)

Looks like I have total different behaviour using an older mariadb version, is there also a different docker-compose for MySQL?

@snipe
Copy link
Owner

snipe commented Feb 18, 2025

This is just regular docker installed in Rancher OS

I honestly know very little about Rancher OS so I'm not sure :(

@leandrobelite
Copy link
Author

@snipe worth to ask,

Is it possible to run Snipe with an older MariaDB version in it latest stable version (7.1.16)? Because if that is the case I could try troubleshooting that meanwhile I wait for my Ubuntu host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docker ❓ not sure if bug This issue has not been confirmed as a bug yet
Projects
None yet
Development

No branches or pull requests

3 participants