portainer: Portainer local unresponsive and slow
Before you start please confirm the following.
- Yes, I’ve searched similar issues on GitHub.
- Yes, I’ve checked whether this issue is covered in the Portainer documentation or knowledge base.
Problem Description
the web ui gets slow and unresponsive. A simple container action takes ages to load to the point where it’s unusable anymore. This used to go away after a few restarts of the machine, I used to get a lucky boot where everything worked perfect. There is no excessive CPU/RAM/DISK load, everything is on idle and all other containers are fast and responsive.
Even focusing on an other tab and back to portainer tab triggers a slow load that might last 3-4 minutes.
Updated to latest
Expected Behavior
fast
Actual Behavior
slow
Steps to Reproduce
any action takes ages of loading.
Portainer logs or screenshots
please let me know what logs you need.
Portainer version
2.21.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker
OS and Architecture
Ubuntu 22.04 amd64
Browser
any
What command did you use to deploy Portainer?
docker run -d -p 8000:8000 -p 9000:9000 -p 9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.21.4
Additional Information
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 3
- Comments: 38
Encountered this myself and had to restart docker host. After a few hours it was back.
I suspect it was related to/caused by 2 containers having the same mac address…
When diagnosing networking issues between containers after the reboot I discovered 2 sharing a MAC address (
not sure how docker did thatlooks like this is a portainer issue itself https://github.com/moby/moby/issues/48595#issuecomment-2398954695 https://github.com/moby/moby/issues/48082#issuecomment-2228713351 ). As soon as I shut down one of the 2 sharing a MAC down (via docker cli since portainer wasn’t loading) portainer started working again. Was then able to bring it back up via portainer and it got a new MAC and portainer continued working.I’m seeing the same issue on current Portainer-CE 2.30.0. All my Docker enviroments are connected through Portainer Edge Agent.
Especially (or only) for the machine, Portainer is running on, I see the following issue - Once I delete a container or deploy a stack, the result is that portainer is completely frozen. I sometimes even need to restart the whole server. There is no difference wether the local docker is conntacted via socket or portainer agent.
This makes portainer usless for me in this case… 😦
Any help is appreciated. Thanks!
when having a look at the browser trace, it seems that the slow response times are mainly when “useLoadCurrentUser” is called. Not really sure if this is the causing issue or just a side effect
Restart of server helps in most cases, sometimes a second or third restart is needed
Many thanks tomarigr, oddly that indeed fixed my issue!
the key here in the “turn it off”. Restart doesn’t always do the trick, it’s important to shut down. Not saying that this is a fix, but at least can get you going.
I’m having the same issue with the latest version (2.21.4), other version were perfectly fine.
It just seems to hang randomly, no extreme resource usage, just unresponsive.