@mdegat01 Thanks for creating this container and filling the void left by Grafana.

Thought I'd share how to use this container on a standalone docker install in case others use Home Assistant Container. This uses /ready to perform a healthcheck and also passes through the host name of the docker host for use in the config. This has been tested on a Pi 4 running rasbian 10 buster.

Create the promtail folder:
mkdir -p ~/promtail && cd ~/promtail

Change the following in promtail.yaml

• clients: url to the IP of the machine running Loki

Save the files below in the ~/promtail folder made above and remove the .txt extensions.
run_promtail.sh.txt
docker-compose.yaml.txt
promtail.yaml.txt

Make sure run_promtail.sh is executable
sudo chmod a+x ~/promtail/run_promtail.sh

Create the container
sudo docker-compose up -d

Verify metrics
wget -qO- http://localhost:9080/metrics

Verify readiness
wget -qO- http://localhost:9080/ready

I am playing with the official loki sample.

I've seen that aarm64 (arm64v8) archs do not have built in journal support.

That's why I am trying to use your promtail-journal in a docker container. I got confused by your explanation that it is only a build container. So could you please explain how to replace your solution within the sample mentioned above?

A few side-questions I've been thinking about but didn't come to answers yet:

1. How can it be checked on a running promtail (container) instance, whether it has built in journal support or not? I might see a warning in logs that it is tried to consult the journal without having built in journal support. But isn't there an option for earlier diagnosis?
2. Will a docker container need a full blown systemd setup to make use of promtail's journal support? Or what else does it mean to services around when having journal support?
3. Is it right, that journal files must be located inside the container with promtail running? Does the location need to be /var/log/jornal?

Thanks for advices.
Greetings woodz