amir20 / dozzle

Realtime log viewer for docker containers.
https://dozzle.dev/
MIT License
5.7k stars 287 forks source link

broken log level badge #3234

Open FrancYescO opened 2 weeks ago

FrancYescO commented 2 weeks ago

🔍 Check for existing issues

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: image

💻 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 commented 2 weeks ago

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

FrancYescO commented 2 weeks ago

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 commented 2 weeks ago

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 commented 2 weeks ago

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 commented 2 weeks ago

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.