[Enhancement]: docker-autoheal #2826

adam commented

@DieselTech commented on GitHub (Jun 4, 2025):

You can implement your own health check in your docker-compose file if this is something you want. Baking the health check into the image and forcing people to use it who doesn't want / need it isn't the way to go.

@DieselTech commented on GitHub (Jun 4, 2025): You can implement your own health check in your docker-compose file if this is something you want. Baking the health check into the image and forcing people to use it who doesn't want / need it isn't the way to go.

adam commented

@skyzuma commented on GitHub (Jun 4, 2025):

my problem is "SQLITE_BUSY: database is locked" (listening a book and abs makes a backup on the same time), so i "need" this :)

@skyzuma commented on GitHub (Jun 4, 2025): my problem is "SQLITE_BUSY: database is locked" (listening a book and abs makes a backup on the same time), so i "need" this :)

adam commented

@skyzuma commented on GitHub (Jun 4, 2025):

You can implement your own health check in your docker-compose file if this is something you want. Baking the health check into the image and forcing people to use it who doesn't want / need it isn't the way to go.

iam on unraid, i dont use docker compose ...

@skyzuma commented on GitHub (Jun 4, 2025): > You can implement your own health check in your docker-compose file if this is something you want. Baking the health check into the image and forcing people to use it who doesn't want / need it isn't the way to go. iam on unraid, i dont use docker compose ...

adam commented

@DieselTech commented on GitHub (Jun 4, 2025):

iam on unraid, i dont use docker compose ...

Then you're missing out on features that would solve your problem.

@DieselTech commented on GitHub (Jun 4, 2025): > iam on unraid, i dont use docker compose ... Then you're missing out on features that would solve your problem.

adam commented

@nichwall commented on GitHub (Jun 4, 2025):

The healthcheck doesn't check for whether the database is locked. I don't use unraid, but there should be a way to add a healthcheck using advanced options or similar. If there is not a way to use advanced options, I would recommend switching to docker compose, which looks to be supported on unraid.

@nichwall commented on GitHub (Jun 4, 2025): The healthcheck doesn't check for whether the database is locked. I don't use unraid, but there should be a way to add a healthcheck using advanced options or similar. If there is not a way to use advanced options, I would recommend switching to docker compose, which looks to be supported on unraid.

adam commented

@skyzuma commented on GitHub (Jun 4, 2025):

iam sry for asking things ...

@skyzuma commented on GitHub (Jun 4, 2025): iam sry for asking things ...

adam commented

@nichwall commented on GitHub (Jun 4, 2025):

No worries.

Looks like you can toggle the advanced view to add a healthcheck https://forums.unraid.net/topic/128044-where-are-extra-parameters/

@nichwall commented on GitHub (Jun 4, 2025): No worries. Looks like you can toggle the advanced view to add a healthcheck https://forums.unraid.net/topic/128044-where-are-extra-parameters/

adam commented

@skyzuma commented on GitHub (Jun 4, 2025):

the advanced view / extra parameters is known but idk what i enter for healthchek so the auto-heal can restart the abs contrainer ...

"The healthcheck doesn't check for whether the database is locked."

if a user is listening to a book and the same time abd is making a backup results in a container crash cause of SQLITE_BUSY: database is locked ... https://github.com/advplyr/audiobookshelf/issues/1910#issue-1806422035 ...

idk if a healthcheck is helpful ... so is ask here for help but i get: use docker compose > make ur own healthcheck > done ...

iam on unraid and since i use this i never needed to use docker compose ... now i need it ? why?

this is mega OT so iam done ...

@skyzuma commented on GitHub (Jun 4, 2025): the advanced view / extra parameters is known but idk what i enter for healthchek so the auto-heal can restart the abs contrainer ... "The healthcheck doesn't check for whether the database is locked." if a user is listening to a book and the same time abd is making a backup results in a container crash cause of SQLITE_BUSY: database is locked ... https://github.com/advplyr/audiobookshelf/issues/1910#issue-1806422035 ... idk if a healthcheck is helpful ... so is ask here for help but i get: use docker compose > make ur own healthcheck > done ... iam on unraid and since i use this i never needed to use docker compose ... now i need it ? why? this is mega OT so iam done ...

adam commented

@nichwall commented on GitHub (Jun 4, 2025):

If you are just wanting the container to restart after a crash, you can add restart: always or restart: unless-stopped.

@nichwall commented on GitHub (Jun 4, 2025): If you are just wanting the container to restart after a crash, you can add `restart: always` or `restart: unless-stopped`.

adam commented

@skyzuma commented on GitHub (Jun 4, 2025):

any healthcheck for #1910 or restart policy will not work cause of "the progress of the streaming cant publish to the db" after a restart (crash based or manual)

a restart policy will work, so the conatainer is up again but without progress sync ...

@skyzuma commented on GitHub (Jun 4, 2025): any healthcheck for #1910 or restart policy will not work cause of "the progress of the streaming cant publish to the db" after a restart (crash based or manual) a restart policy will work, so the conatainer is up again but without progress sync ...

adam commented

@nichwall commented on GitHub (Jun 4, 2025):

any healthcheck for #1910 or restart policy will not work cause of "the progress of the streaming cant publish to the db" after a restart (crash based or manual)

a restart policy will work, so the conatainer is up again but without progress sync ...

Does using a healthcheck not cause the server to restart? Everything I have read about health checks says that the container/service is restarted.

@nichwall commented on GitHub (Jun 4, 2025): > any healthcheck for #1910 or restart policy will not work cause of "the progress of the streaming cant publish to the db" after a restart (crash based or manual) > > a restart policy will work, so the conatainer is up again but without progress sync ... Does using a healthcheck not cause the server to restart? Everything I have read about health checks says that the container/service is restarted.

adam commented

@skyzuma commented on GitHub (Jun 4, 2025):

iam sry, was my fault ... i never testest with a healthcheck (idk how this working on unraid) ... i only tested with the restart policy ... (
Extra Parameters: --restart unless-stopped (this is working and the container is restarting))

@skyzuma commented on GitHub (Jun 4, 2025): iam sry, was my fault ... i never testest with a healthcheck (idk how this working on unraid) ... i only tested with the restart policy ... ( Extra Parameters: --restart unless-stopped (this is working and the container is restarting))

adam commented