I don't think this is related to switching between containers. I haven't seen any body else report this. Most likely it is related to something Podman is doing. The code:

message += tail[32:]  // I skip the first 32 chars because it is timestamp 

I am not sure how to fix this because I haven't actually seen it.

1. Are you sure it is when you switch containers? If you go directly to the container does it still do that?
2. Can you do export of the logs of the containers that is breaking this?

I could take a guess and try to fix it but I think something else is happening.

Yes, this issue only happens when I start switching between containers (it usually fails on the second or third switch).

It starts working again only after restarting. Once it does, reaching dozzle/container/<id> does not cause it to crash.

Exporting logs also doesn’t seem to trigger the crash.

Please note that I have tested with & without :
DOZZLE_ENABLE_SHELL=true

Yes, this issue only happens when I start switching between containers (it usually fails on the second or third switch).

Hmm that is really weird.

Sorry I wasn't clear. Can you attach the logs? I can run it locally and see if something is happening.

🤔 I don't know what is causing this to be honest.

Also, not sure if you can help out, but test it on Docker? I am trying to narrow down if this is only happening on Podman or if it's something different with your cotnainers.

I've seen a similar bug in a similar environment (Podman), but unfortunately, I couldn't recreate the issue. It's probably related to the content of the log.

It would definitely help to verify that there are at least 32 characters in the tail variable before skipping it. Then, we would not get a panic, and we could see in Dozzle what Podman is actually sending.

@ivoshm @karami4yasser I created a new Ubuntu VM and installed podman version 5.4.1. I did

podman run --volume /run/user/501/podman/podman.sock:/var/run/docker.sock -d -p 8080:8080 docker.io/amir20/dozzle:latest

Then did a bunch of fake containers. I switched around for 20+ times and nothing broke.

I would need to see the content of logs to help or somehow reproduce it.