Is there an existing issue for this? <li class="

I'm seeing the exact same problem as <a class="user-mention notranslate"

Will add our hint about using docker compose V2 from <a href="https://docs.teslamate.o

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Different language, same thing: <a class="issue-link js-issue-link" data-error-text="F

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Upgrading via docker-compose from v1.28.3 to v1.28.4 results in unusable system with "404 page not found" error about teslamate HOT 14 CLOSED

SemoTech commented on July 22, 2024 1

Upgrading via docker-compose from v1.28.3 to v1.28.4 results in unusable system with "404 page not found" error

from teslamate.

Comments (14)

SemoTech commented on July 22, 2024 2

I'm seeing the exact same problem as @SemoTech

Downgraded to 1.28.3 and working fine.

Exactly @ibmaster, Teslamate v1.28.3 works fine in Docker v19, but upgrading to v1.28.4 while still using Docker v19 brakes Teslamate.

I 1st upgraded from Docker version 19.03.7, build 7141c199a2 to Docker version 26.0.0, build 2ae903e

Then rebooted & checked previous Teslamate version, and can confirm v1.28.3 runs fine on new Docker v26

I then re-did the docker compose update for Teslamate using "docker-compose pull && docker-compose up -d" and Teslamate v1.28.4 is now working with Docker v26 and without any more "404 page not found" errors!!!!

So issue was Docker v19 needing to be upgraded to V26 BEFORE upgrading from Teslamate v1.28.3 to v1.28.4 (may work in V20 too)

Thank you all for your help!

from teslamate.

ibmaster commented on July 22, 2024 1

Yes, I updated to Docker 20 and teslamate 1.28.4 is working now for me.

…

On Mar 20, 2024, at 3:55 PM, SemoTech ***@***.***> wrote: I'm seeing the exact same problem as @SemoTech <https://github.com/SemoTech> Downgraded to 1.28.3 and working fine. Exactly @ibmaster <https://github.com/ibmaster>, Teslamate v1.28.3 works fine in Docker v19, but upgrading to v1.28.4 while still using Docker v19 brakes Teslamate. I 1st upgraded from Docker version 19.03.7, build 7141c199a2 to Docker version 26.0.0, build 2ae903e Then rebooted & checked previous Teslamate version, and can confirm v1.28.3 runs fine on new Docker v26 I then re-did the docker compose update for Teslamate using "docker-compose pull && docker-compose up -d" and Teslamate v1.28.4 is now working with Docker v26 and without any more "404 page not found" errors!!!! So issue was Docker v19 needing to be upgraded to V26 BEFORE upgrading from Teslamate v1.28.3 to v1.28.4 (may work in V20 too) Thank you all for your help! — Reply to this email directly, view it on GitHub <#3754 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJWC2EGCZQTVERNK3BDJXWDYZIHV5AVCNFSM6AAAAABFAEXPKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJQHAZTANRQGA>. You are receiving this because you were mentioned.

from teslamate.

JakobLichterfeld commented on July 22, 2024 1

Will add our hint about using docker compose V2 from https://docs.teslamate.org/docs/maintenance/backup_restore/ also on installation documentation, even if it already links to docker compose v2

from teslamate.

cwanja commented on July 22, 2024

Several had updated to 1.28.4 without issues, so I tend to believe this is not an “issue”, but will leave it for the moment.

What is your storage like on the host device? What does your YML file look like? What version of docker are you running?

from teslamate.

SemoTech commented on July 22, 2024

Several had updated to 1.28.4 without issues, so I tend to believe this is not an “issue”, but will leave it for the moment.

What is your storage like on the host device? What does your YML file look like? What version of docker are you running?

@cwanja Chris, this is a Vultr VM running CentOS 7 with 25GB Storage and Docker version 19.03.7, build 7141c199a2

Here is the rest of the info (restored back to v1.28.3 using a backup image, BEFORE the update to v1.28.4 which consistently fails):

[root@teslamate ~]# docker ps
CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                                      NAMES
1c43fa5a5fdf        teslamate/teslamate:latest   "tini -- /bin/sh /en‚Ä¶"   6 weeks ago         Up About an hour    4000/tcp                                   root_teslamate_1
05db1ee60217        teslamate/grafana:latest     "/run.sh"                6 weeks ago         Up About an hour    3000/tcp                                   root_grafana_1
6147aa002265        postgres:12                  "docker-entrypoint.s‚Ä¶"   6 weeks ago         Up About an hour    5432/tcp                                   root_database_1
ed9c932e0fb1        eclipse-mosquitto:1.6        "/docker-entrypoint.‚Ä¶"   9 months ago        Up About an hour    127.0.0.1:1883->1883/tcp                   root_mosquitto_1
b92bd163fb82        traefik:v2.1                 "/entrypoint.sh --gl‚Ä¶"   3 years ago         Up About an hour    0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   root_proxy_1
[root@teslamate ~]# 
[root@teslamate ~]# 
[root@teslamate ~]# docker inspect 1c43fa5a5fdf | grep com.docker.compose
                "com.docker.compose.config-hash": "15736609df597e3fc789ffebb873510e81ff647ec4ac41b4a36880fec729d306",
                "com.docker.compose.container-number": "1",
                "com.docker.compose.oneoff": "False",
                "com.docker.compose.project": "root",
                "com.docker.compose.project.config_files": "docker-compose.yml",
                "com.docker.compose.project.working_dir": "/root",
                "com.docker.compose.service": "teslamate",
                "com.docker.compose.version": "1.25.4",
[root@teslamate ~]# 
[root@teslamate ~]# cat docker-compose.yml
version: '3'

services:
  teslamate:
    image: teslamate/teslamate:latest
    restart: always
    depends_on:
      - database
    environment:
      - ENCRYPTION_KEY=${TM_ENCRYPTION_KEY} 
      - DATABASE_USER=${TM_DB_USER}
      - DATABASE_PASS=${TM_DB_PASS}
      - DATABASE_NAME=${TM_DB_NAME}
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
      - VIRTUAL_HOST=${FQDN_TM}
      - CHECK_ORIGIN=true
      - TZ={$TM_TZ}
    volumes:
      - ./import:/opt/app/import
    labels:
      - "traefik.enable=true"
      - "traefik.port=4000"
      - "traefik.http.middlewares.redirect.redirectscheme.scheme=https"
      - "traefik.http.middlewares.auth.basicauth.usersfile=/auth/.htpasswd"
      - "traefik.http.routers.teslamate-insecure.rule=Host(`${FQDN_TM}`)"
      - "traefik.http.routers.teslamate-insecure.middlewares=redirect"
      - "traefik.http.routers.teslamate-ws.rule=Host(`${FQDN_TM}`) && Path(`/live/websocket`)"
      - "traefik.http.routers.teslamate-ws.entrypoints=websecure"
      - "traefik.http.routers.teslamate-ws.tls"
      - "traefik.http.routers.teslamate.rule=Host(`${FQDN_TM}`)"
      - "traefik.http.routers.teslamate.middlewares=auth"
      - "traefik.http.routers.teslamate.entrypoints=websecure"
      - "traefik.http.routers.teslamate.tls.certresolver=tmhttpchallenge"
    cap_drop:
      - all

  database:
    image: postgres:12
    restart: always
    environment:
      - POSTGRES_USER=${TM_DB_USER}
      - POSTGRES_PASSWORD=${TM_DB_PASS}
      - POSTGRES_DB=${TM_DB_NAME}
    volumes:
      - teslamate-db:/var/lib/postgresql/data

  grafana:
    image: teslamate/grafana:latest
    restart: always
    environment:
      - DATABASE_USER=${TM_DB_USER}
      - DATABASE_PASS=${TM_DB_PASS}
      - DATABASE_NAME=${TM_DB_NAME}
      - DATABASE_HOST=database
      - GRAFANA_PASSWD=${GRAFANA_PW}
      - GF_SECURITY_ADMIN_USER=${GRAFANA_USER}
      - GF_SECURITY_ADMIN_PASSWORD=${GRAFANA_PW}
      - GF_AUTH_BASIC_ENABLED=true
      - GF_AUTH_ANONYMOUS_ENABLED=false
      - GF_SERVER_ROOT_URL=https://${FQDN_GRAFANA}
      - GF_SMTP_ENABLED=true
      - GF_SMTP_FROM_NAME=${GF_SMTPNAME}
      - GF_SMTP_FROM_ADDRESS=${GF_SMTPSENDER}
      - GF_SMTP_HOST=${GF_SMTPHOST}                      
      - GF_SMTP_USER=${GF_SMTPUSER}                   
      - GF_SMTP_PASSWORD=${GF_SMTPPASS}
      - GF_SMTP_SKIP_VERIFY=false
    volumes:
      - teslamate-grafana-data:/var/lib/grafana
    labels:
      - 'traefik.enable=true'
      - 'traefik.port=3000'
      - "traefik.http.middlewares.redirect.redirectscheme.scheme=https"
      - "traefik.http.routers.grafana-insecure.rule=Host(`${FQDN_GRAFANA}`)"
      - "traefik.http.routers.grafana-insecure.middlewares=redirect"
      - "traefik.http.routers.grafana.rule=Host(`${FQDN_GRAFANA}`)"
      - "traefik.http.routers.grafana.entrypoints=websecure"
      - "traefik.http.routers.grafana.tls.certresolver=tmhttpchallenge"

  mosquitto:
    image: eclipse-mosquitto:1.6
    restart: always
    ports:
      - 127.0.0.1:1883:1883
    volumes:
      - mosquitto-conf:/mosquitto/config
      - mosquitto-data:/mosquitto/data

  proxy:
    image: traefik:v2.1
    restart: always
    command:
      - "--global.sendAnonymousUsage=false"
      - "--providers.docker"
      - "--providers.docker.exposedByDefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.tmhttpchallenge.acme.httpchallenge=true"
      - "--certificatesresolvers.tmhttpchallenge.acme.httpchallenge.entrypoint=web"
      - "--certificatesresolvers.tmhttpchallenge.acme.email=${LETSENCRYPT_EMAIL}"
      - "--certificatesresolvers.tmhttpchallenge.acme.storage=/etc/acme/acme.json"
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./.htpasswd:/auth/.htpasswd
      - ./acme/:/etc/acme/
      - /var/run/docker.sock:/var/run/docker.sock:ro

volumes:
    teslamate-db:
    teslamate-grafana-data:
    mosquitto-conf:
    mosquitto-data:

[root@teslamate ~]#

And here is the Disk Info:

[root@teslamate ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        486M     0  486M   0% /dev
tmpfs           496M     0  496M   0% /dev/shm
tmpfs           496M   14M  483M   3% /run
tmpfs           496M     0  496M   0% /sys/fs/cgroup
/dev/vda1        25G   21G  2.9G  88% /
overlay          25G   21G  2.9G  88% /var/lib/docker/overlay2/2ac80dcfcfc0b29422a298707011cb68b550accd20f98d7cdf3053d4a4671741/merged
overlay          25G   21G  2.9G  88% /var/lib/docker/overlay2/cb479ef70c841337e30f1ebd32ccb31ad17219bc47cac3cb26786624b8f04932/merged
overlay          25G   21G  2.9G  88% /var/lib/docker/overlay2/bfaf718c1d2ab6bd5763ba6b7a9aeee5910f543f515c6167c09f53c7a10753f6/merged
overlay          25G   21G  2.9G  88% /var/lib/docker/overlay2/b308ea0f03b58ac32a402bff029820f857f14df237aedce28841559b5fa1e779/merged
overlay          25G   21G  2.9G  88% /var/lib/docker/overlay2/48e1546345205153f5ac85429757fef423100eb36132085ac27ff383bb02e745/merged
shm              64M     0   64M   0% /var/lib/docker/containers/05db1ee602178b0dd07ece68005c83ad2b887dc85293633f0c02831fe3648ce7/mounts/shm
shm              64M     0   64M   0% /var/lib/docker/containers/1c43fa5a5fdf94c60716f4d2ba6fb4cbecfdf6dfd00e68db22991f7a51bf91f1/mounts/shm
shm              64M  408K   64M   1% /var/lib/docker/containers/6147aa0022656f2b2593735ab6bfbf6adc6ffa1f651649b0a31ac4431f9e933b/mounts/shm
shm              64M     0   64M   0% /var/lib/docker/containers/b92bd163fb82008f0c22f55ace17a6218f3d67228c8faee08fe770af0fabe46b/mounts/shm
shm              64M     0   64M   0% /var/lib/docker/containers/ed9c932e0fb14350c3de0a4123eff956b65695c75a2858f928c202eb4d654ded/mounts/shm
tmpfs           100M     0  100M   0% /run/user/0
[root@teslamate ~]#

Again, all up to and including v1.28.3 works just fine, but breaks upgrading to v1.28.4

from teslamate.

cwanja commented on July 22, 2024

@JakobLichterfeld @brianmay were there any dependencies added to 1.28.4 that would break an install like this?

from teslamate.

brianmay commented on July 22, 2024

It works for me! :-)

I think Elixir was on 1.16.1 already. We did change the tag from 1.16 to 1.16.1-otp-26, but I think these are the same thing (at least when the images were built - 1.16.2 has been released now).

Google search shows me https://stackoverflow.com/questions/76703987/rabbitmq-docker-failed-to-create-thread-operation-not-permitted-1 - I think rabbitmq runs on the beam VM also.

What version of Docker do you have? Can you upgrade this?

from teslamate.

brianmay commented on July 22, 2024

https://www.reddit.com/r/docker/comments/vc1rkn/comment/josuq7c/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

The latest glibc now attempts to use 'clone3' by default. For backwards compatibility it will look for ENOSYS errno and fallback to "clone". The EPERM errno meanwhile is treated as a fatal error.

from teslamate.

brianmay commented on July 22, 2024

Different language, same thing: docker-library/redmine#307

Basically I think either libseccomp and docker need to be upgraded.

But adding the following to docker-compose.yaml might help also (not tested!):

security_opt:
      - seccomp:unconfined

from teslamate.

SemoTech commented on July 22, 2024

Hi @brianmay I am currently running Docker version 19.03.7, build 7141c199a2

from teslamate.

brianmay commented on July 22, 2024

I think it needs to be at least v20, first reported success is with v20.10.

from teslamate.

SemoTech commented on July 22, 2024

I think it needs to be at least v20, first reported success is with v20.10.

Got it, thanks, let me see about upgrading Docker 1st and then I will retry upgrading Teslamate....

from teslamate.

ibmaster commented on July 22, 2024

I'm seeing the exact same problem as @SemoTech

Downgraded to 1.28.3 and working fine.

from teslamate.

ttytyper commented on July 22, 2024

Different language, same thing: docker-library/redmine#307

Basically I think either libseccomp and docker need to be upgraded.

But adding the following to docker-compose.yaml might help also (not tested!):
security_opt:
      - seccomp:unconfined

Thanks, that solved it for me. Running on a old Debian Buster where Docker 18.09.1 is the latest available version. All other packages also at latest available versions. Ran into the exact same "Operation not permitted" errors as OP described when upgrading Teslamate to v1.28.4 today. Adding your suggestion to the teslamate section in docker-compose.yml made it work again.

from teslamate.

Upgrading via docker-compose from v1.28.3 to v1.28.4 results in unusable system with "404 page not found" error about teslamate HOT 14 CLOSED

Comments (14)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent