Replies: 4 comments
-
After some more time, I found out that aother container that had access to the socket via a volume was having troubles. Then the cli tool i keep this open as it is still an unhandled exception and don't know if it needs investigations. But I have no more problem. Thanks for the good work <3 |
Beta Was this translation helpful? Give feedback.
-
@BancarelValentin Thank you for the update. I am glad to hear you are able to move forward. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
having the same issue. my docker has a container in removing state:
this container doesn't have a name anymore. as a result the name column can't be rendered: name.tsx export const name: Column = { maybe it would make sense to validate if the name is not null or empty instead of trying to trim the string without any validation |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug description
When trying to access the container list (in an environement) the page is blank (except from the nav on the left) and when opening the console there is a JS error
Expected behavior
List of all my containers
Portainer Logs
JS logs:
Docker logs :
Steps to reproduce the issue:
Technical details:
Additional context
Extract of compose file:
Full version
Screen of the blank page and the error in the console:

Beta Was this translation helpful? Give feedback.
All reactions