broken log level badge

[FrancYescO]

🔍 Check for existing issues

• Completed

How is Dozzle deployed?

Standalone Deployment

📦 Dozzle version

8.2.1

✅ Command used to run Dozzle

🐛 Describe the bug / provide steps to reproduce it

This is an excerpt from official docker registry container log... seems the parser does not really like the format:

💻 Environment

📸 If applicable, add screenshots to help explain your bug

No response

📜 If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.

No response

[amir20]

Can you give me the docker run you used to run this. I don't run this container.

[FrancYescO]

docker run -d -p 5000:5000 --restart always --name registry registry:2

a few request to /v2/_catalog?n=1000 should be enough to have a similar log

[amir20]

I tried running registry:2 and got access denied. Haven't had much time to look at the README file. So I'll come back to it when I have time.

[FrancYescO]

hmm i just retried and i can confirm that a simple GET request to http://127.0.0.1:5000/v2/_catalog?n=1000 also issued from browser is working flawless (and gives {"repositories":[]} as response) .... maybe you have port 5000 user from something else?

[amir20]

Good guess. Port 5000 was something else. I would have never guessed that.

I see the problem. Not sure what is causing it. It's not as bad as I thought though.

[amir20]

Coming back this I think I know what is going on. I won't be able to fix it. The logic for grouping logs together with same level is if they are very close to each timer with timestamp. It does create false positives and this is one of those cases. I don't think I can do anything about it as I am just guessing the levels.