flame icon indicating copy to clipboard operation
flame copied to clipboard

[BUG] Applications fail to load - [ERROR] containers.filter is not a function

Open cbenning opened this issue 3 years ago • 6 comments

Deployment details:

  • App version [e.g. v1.7.4]: v2.1.1
  • Platform [e.g. amd64, arm64, arm/v7]: amd64
  • Docker image tag [e.g. latest, multiarch]: 2.1.1

Bug description:

After logging in, the Applications section just loads forever. When I do docker logs -f flame I see:

[ERROR] containers.filter is not a function

repeated each time I refresh the page.


Steps to reproduce:

Docker-compose:

  flame:
    image: pawelmalak/flame:2.1.1
    container_name: flame
    volumes:
      - /<path>/flame:/app/data
      - /var/run/docker.sock:/var/run/docker.sock 
    ports:
      - 80:5005
    environment:
      - PASSWORD=<password>
    restart: unless-stopped
  1. docker-compose up -d
  2. Open http://:80 in browser
  3. Enter password
  4. Applications section loads forever

cbenning avatar Dec 04 '21 18:12 cbenning

Can you show your config file?

pawelmalak avatar Dec 07 '21 15:12 pawelmalak

{
   "WEATHER_API_KEY":"",
   "lat":0,
   "long":0,
   "isCelsius":true,
   "customTitle":"Flame",
   "pinAppsByDefault":true,
   "pinCategoriesByDefault":true,
   "hideHeader":false,
   "useOrdering":"orderId",
   "appsSameTab":false,
   "bookmarksSameTab":false,
   "searchSameTab":true,
   "hideApps":false,
   "hideCategories":false,
   "hideSearch":false,
   "defaultSearchProvider":"l",
   "dockerApps":true,
   "dockerHost":"<ip>",
   "kubernetesApps":false,
   "unpinStoppedApps":false,
   "useAmericanDate":false,
   "disableAutofocus":false,
   "greetingsSchema":"Good evening!;Good afternoon!;Good morning!;Good night!",
   "daySchema":"Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday",
   "monthSchema":"January;February;March;April;May;June;July;August;September;October;November;December",
   "showTime":false,
   "defaultTheme":"tron",
   "isKilometer":true,
   "weatherData":"cloud",
   "hideDate":false
}

cbenning avatar Dec 07 '21 23:12 cbenning

Has it worked before or are you setting it up for the first time?

pawelmalak avatar Dec 08 '21 15:12 pawelmalak

I had set it up for the first time and it was working for a few days. Then suddenly it stopped responding and I found the above message. I have a weekly docker-compose auto-pull and restart so I assume it updated in there somewhere? Not sure.

For now I've switch to Homer so I don't have it running anymore.

cbenning avatar Dec 08 '21 17:12 cbenning

I am encountering the same issue as well. Started today. Been running Flame for about 6 months and this issue just popped up out of the blue.

image

image

pierrebuckley avatar Jan 06 '22 04:01 pierrebuckley

I am having the same issue.

New setup.

Went back through the versions to v2.0.0 with no change. EDIT: I had to wipe the appdata directory and start from scratch. v2.1.0 is working. I will update until it breaks.

EDIT2: Ok, so it works upgrading all the way through to 2.2.1

The only thing I can think of right now is that I did not have any flame labels on my containers when I started this and added labels as a troubleshooting step. It never fixed itself, but nuking the appdata and restarting worked. Why it would break in the middle of it working is beyond me. Hopefully this info helps.

bencmeyer avatar Jan 26 '22 15:01 bencmeyer