Add a flag to force unlocking the database tables at startup about traccar-docker

[tananaev]

I personally like the clean solution we have now. I feel like it's in a true spirit of Docker.

I'm also not sure if locked database is a real issue. Database is temporarily locked only on launch, so even if you lose battery and shutdown the server after the launch, it shouldn't happen.

[meilon]

I'm against hard coding this into the container because I don't use H2, instead I use MariaDB.
Instead I'd welcome moving to an entrypoint.sh which actually starts traccar (and not using CMD). This script could check if a file exists at a predefined location and execute it. This way pre-start would be customizable without rebuilding the image.

Maybe migrating over to s6-overlay or how linuxserver.io does it makes using this container more like the others without special implementations

[krasi-georgiev]

yes an entrypoint file would work.

[krasi-georgiev]

any comment from the maintainers?

[krasi-georgiev]

ping

[krasi-georgiev]

ping

[tananaev]

I agree that it doesn't make sense to hardcode something like this.

[krasi-georgiev]

@tananaev the question is for this change

Instead I'd welcome moving to an entrypoint.sh which actually starts traccar (and not using CMD). This script could check if a file exists at a predefined location and execute it. This way pre-start would be customizable without rebuilding the image.

[krasi-georgiev]

It happened few times where it went into a lockdown and need manual intervention

[tananaev]

It means that it happened during service startup, which probably means you need to investigate more why it happened first before implementing any patches. Startup should only take a few seconds, so the chances that shutdown happens at the same time should be very low. There has to be an explanation for why it happened so many times for you.

[krasi-georgiev]

yes I think you are right it did happen during initialization. so lets leave as is and will spend more time on this when/if needed