The status of the Docker container is always unhealthy for some reason

[lzrdblzzrd]

For some unknown reason, the health status of the ASF container in Docker is always unhealthy, even when ASF is running perfectly and without any errors. This only happens on the latest branch; there is no such issue on the released branch. The container status on the released branch becomes running after ASF completes the launch of all bots.

[JustArchi]

I can't reproduce, works fine for me.

Healthcheck depends on pidof -q ArchiSteamFarm; echo $? command, you can try getting into container with docker exec -it archisteamfarm /bin/bash and checking out what above command returns. If it's non-zero result, then that's your reason for container being unhealthy. The question is why it happens, and the answer is likely something to do with your host machine, although I'm not sure what - you can try digging.

[lzrdblzzrd]

Yes, sure.

[JustArchi]

According to docker specs, if healthcheck command fails 3 times in a row, with timeout also being failure, container is considered unhealthy and likely doesn't return back to healthy anymore.

I'm not sure what happened in your case, but perhaps for some reason the healthcheck didn't complete in time or the process crashed for a longer while inside container - maybe your plugins or something similar.

Try restarting the container and see if the issue happens again. If yes, this suggests some machine issue, as I don't see how the command could fail otherwise as of now.

[lzrdblzzrd]

I just disabled all my plugins, but ASF still has an unhealthy status. In fact, this issue arose quite a while ago and was only on the latest branch, but I decided to write about it only now. I have no idea why this could be happening at all if ASF returns an error code of 0.

[JustArchi]

Well I don't have a solution for you, it works on my machine and docker should be cross-OS and cross-machine compatible.

As additional verification I've tried to reproduce your issue also on my Raspberry Pi 4 running Debian on aarch64, and also couldn't reproduce:

I don't have other solutions or recommendations, you can try digging further if you want to, but it works fine for me.

For reference: docker -v on my machine is Docker version 20.10.25+dfsg1, build b82b9f3. I've tried to reproduce with docker run -it --pull always --rm --name asf justarchi/archisteamfarm.

[lzrdblzzrd]

Docker on my RPi Docker version 24.0.7, build afdd53b.
I suppose it may be somehow related to DietPi OS.
I don't think I'll be able to solve this problem myself, so I'll just continue to ignore it as it doesn't affect the ASF's work in any way.
Thank you for your time!

[JustArchi]

Yeah, you can ignore the healthcheck or even disable it if you want to, with --no-healthcheck option. It's not like it does something more than checking if the process is running anyway, since we don't really have a reliable way of testing it, as IPC is not always guaranteed to be up (user might've disabled it).

[lzrdblzzrd]

Thank you, I didn't know that healthcheck can be disabled despite being specified in the Dockerfile.
In a sense, it completely solved my problem ;)