auto-redirect to new container broken

[FrancYescO]

🔍 Check for existing issues

• Completed

How is Dozzle deployed?

Standalone Deployment

📦 Dozzle version

8.0.5

✅ Command used to run Dozzle

README

🐛 Describe the bug / provide steps to reproduce it

this seems was broken with #3098, suggested a solution #3077 (comment) this will also touch this issue #3036

recreate a container, you will not be redirected and will end up to a page saying "no container found" despite the option "auto-redirect to new container w/matching name"

💻 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]

recreate a container, you will not be redirected and will end up to a page saying "no container found" despite the option "auto-redirect to new container w/matching name"

Is the container removed too in this case? Can you tell me which commands are being run? eg. docker stop or docker rm

[amir20]

Ah I see what you mean now. If the container is removed then the page disappears.

I was testing with docker run --rm --name FOO ....

I'll have to think about how to do it better. 🤔

[amir20]

This is going to be tricky because the menu on the left is closely related container view.

[FrancYescO]

i think that if instead of triggering instantly the delete of the container when you get the message from eventstream show an alert message like "container deleted going to remove" and put a timeout a little bigger of the redirect one to new container one will be enought to get all working as it was

[amir20]

I think I have a better idea. I just need to do a soft delete so the container is still there but the menu hides it.

[amir20]

Should be fixed in master now. Give it a try.