Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Containers with the same name keep being recreated[Bug] #27

Closed
KuraiAndras opened this issue Jan 15, 2024 · 1 comment
Closed

Containers with the same name keep being recreated[Bug] #27

KuraiAndras opened this issue Jan 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@KuraiAndras
Copy link

Describe the issue

I have multiple containers shown as sensors, and most of them are unavailable and could only be deleted manually - the problem is that I noticed it late and now I have ~1400 sensors listed in HA and it slows things down a bit.

To be clear: this is connected to Portainer with 2 docker standalone environments and running around 30 containers - definitely not in the thousands.

How to reproduce the issue

🤷‍♂️

Expected behavior

Containers as sensors don't get duplicated

Screenshots

image
image
image

Software versions

  • Home Assistant version: 2024.1.3
  • Portainer integration version: V1.0.2
  • Portainer software version: 2.19.4 BE

Diagnostics data

🤷‍♂️

Traceback/Error logs

🤷‍♂️

Additional context

I am runnig Portainer Business Edition - the problem seems to be is that when I update a stack using Portainer BE and select Re-pull image and redeploy
image
The number of entities goes up by the number of containers in the stack - indicating that this is caused by portainer stopping containers, pulling the latest image and then re deploying them. It also seems that additional container senors in the integration get a new index when they get recreated. For example:
image
image

@KuraiAndras KuraiAndras added the bug Something isn't working label Jan 15, 2024
@tomaae
Copy link
Owner

tomaae commented Jan 15, 2024

duplicate #7

@tomaae tomaae closed this as completed Jan 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Feb 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants