I can't see my containers in Portainer - Version Community Edition 2.33.6 LTS

[davimontenegro-br]

Ask a Question!

I have the community version and it no longer shows my containers. I've already updated to the latest version and validated the settings. The dashboard shows that I have 47, but when I go to the container link, the page doesn't show anything; it's completely blank. Can anyone help me?

[goncaloalves]

A few things to check:

1. Docker socket permissions
Make sure Portainer has access to the Docker socket:

ls -la /var/run/docker.sock

If permissions are wrong, fix with:

sudo chmod 666 /var/run/docker.sock

2. Environment connection
In Portainer, go to Environments and check if your local Docker environment is connected. Click on it and verify the status shows as "connected".

3. Browser cache
Try a hard refresh (Ctrl+Shift+R) or clear browser cache. Sometimes the UI gets stuck.

4. Portainer logs
Check the logs for errors:

docker logs portainer

5. Container list endpoint
Try accessing the API directly: http://your-portainer:9000/api/endpoints/1/docker/containers/json

If the dashboard shows 47 but the list is blank, it is likely a UI/frontend issue rather than a Docker/permission issue. Let me know what you find!

[davimontenegro-br]

Good morning!! First of all, thank you for your attention and help! I followed the procedures and still can't see the containers. A new LTS version (Community Edition 2.33.7 LTS) was released. I performed the update and the containers reappeared. I believe the permissions added to the file as instructed may have helped. Now I have several dead <empty> containers that I can't delete. Every time a new problem arises. Best regards, Davi Em qui., 12 de fev. de 2026 às 18:21, Gonçalo Alves < ***@***.***> escreveu:

…

A few things to check: *1. Docker socket permissions* Make sure Portainer has access to the Docker socket: ls -la /var/run/docker.sock If permissions are wrong, fix with: sudo chmod 666 /var/run/docker.sock *2. Environment connection* In Portainer, go to *Environments* and check if your local Docker environment is connected. Click on it and verify the status shows as "connected". *3. Browser cache* Try a hard refresh (Ctrl+Shift+R) or clear browser cache. Sometimes the UI gets stuck. *4. Portainer logs* Check the logs for errors: docker logs portainer *5. Container list endpoint* Try accessing the API directly: http://your-portainer:9000/api/endpoints/1/docker/containers/json If the dashboard shows 47 but the list is blank, it is likely a UI/frontend issue rather than a Docker/permission issue. Let me know what you find! — Reply to this email directly, view it on GitHub <#13048 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BRWTMA5T4JQGWT3RPXNJKCD4LTVEXAVCNFSM6AAAAACTTDY5V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZYG44TMNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Nick-Portainer]

Hello @davimontenegro-br How did you update? It sounds like your containers may have become orphaned. - https://docs.portainer.io/faqs/troubleshooting/stacks-deployments-and-updates/how-do-i-recover-orphaned-stacks-from-a-previously-deleted-environment

Can you try the above and let me know?

[davimontenegro-br]

Good morning Nick How are you? I installed Portainer using the Orion setup (https://oriondesign.art.br/), upgraded it from there, and the problem was fixed with the new version. Thank you for your help! Regards Abs Davi Montenegro Em dom., 22 de fev. de 2026 às 16:17, Nick Wilkinson < ***@***.***> escreveu:

…

Hello @davimontenegro-br <https://github.com/davimontenegro-br> How did you update? It sounds like your containers may have become orphaned. - https://docs.portainer.io/faqs/troubleshooting/stacks-deployments-and-updates/how-do-i-recover-orphaned-stacks-from-a-previously-deleted-environment Can you try the above and let me know? — Reply to this email directly, view it on GitHub <#13048 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BRWTMA5LEYJEKG5HHUIW3CL4NH6F7AVCNFSM6AAAAACTTDY5V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOBZGA2TAMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>