Open mpfl opened 2 years ago
I have the same error on my new server ^^ The old server work well.
@enzofoucaud Can you share the details of your old server? What practices have you changed when migrating to the new server? Are there any new containers with funky labels you're running?
Okay, this is weird. I just added Flame labels to a couple of more containers and now it works..?
@enzofoucaud Can you share the details of your old server? What practices have you changed when migrating to the new server? Are there any new containers with funky labels you're running?
I use the same step than my old server, same docker-compose
Okay, this is weird. I just added Flame labels to a couple of more containers and now it works..?
example ?
I had only Overseerr and Paperless-NG and was getting the error message. Then I added a weather API key and also Vikunja, TTRSS, and Home Assistant, and it started working.
Don't work form me .. I wait
For future people, I have Flame running for months, and today I noticed that it wasn't able to fetch apps. I got the same error as OP (by searching the error I came across this issue).
The problem was running Vikunja. I stopped that, and suddenly it works again.
Had same problem, as a workaround added flame tags to one of the containers, but I don't really want that container to be on the app list. Seems like the problem manifests itself when some containers don't have flame tags set up.
Can confirm this seems to be a Vikunja + flame incompatibility.
Deployment details:
Bug description:
Trying to define a bunch of things with labels but I seem to be upsetting flame, which makes me sad.
Steps to reproduce:
tecnativa/docker-socket-proxy
for security:I am also running paperless with labels to add it to flame:
[2021-12-06 08:45:29.424 UTC+0] [ERROR] Cannot read properties of undefined (reading 'split')
What else have I tried?
I gave flame temporary access directly to the docker socket but still get the same issue.
I have tried with another application, but still get the same issues.
I'm quite interested in the idea of a label-defined dashboard, so I might poke into this issue on a future weekend.