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

Release 1.28.3 seemingly not correctly pushed as arm64 image #3648

Closed
1 task done
olexs opened this issue Feb 2, 2024 · 1 comment
Closed
1 task done

Release 1.28.3 seemingly not correctly pushed as arm64 image #3648

olexs opened this issue Feb 2, 2024 · 1 comment

Comments

@olexs
Copy link
Contributor

olexs commented Feb 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Having updated my Teslamate install on a Hetzner ARM VPS, I get the latest image that's explicitly tagged as 1.28.3 on Docker Hub. However, the logs show version "1.28.2" and also it tries to use the old (broken) /vehicles endpoint instead of the new /products, and won't start up properly because of that.

Digest of the problematic image is teslamate/teslamate@sha256:56fc36f2f5113d172ec85e17f6e6a8f1c1d44c5d46bc9a6605bb078dbfe2d63b.

On a x64 test machine, the same tag (:latest or explicitly :1.28.3) pulls the correct image that starts up as 1.28.3 and works perfectly. I can only assume that the cross-arch build didn't build and/or push the ARM image correctly.

Expected Behavior

No response

Steps To Reproduce

  1. Use the following docker-compose.yml on an ARM machine:
version: '3'
services:
  teslamate:
    image: teslamate/teslamate:1.28.3
    # add all the rest as usual...
  1. Start it up and observe the logs.

Relevant log output

teslamate-teslamate-1  | 2024-02-02 16:45:24.585 [info] Migrations already up
teslamate-teslamate-1  | 2024-02-02 16:45:26.621 [info] System Info: Erlang/OTP 26 (jit)
teslamate-teslamate-1  | 2024-02-02 16:45:26.621 [info] Version: 1.28.2
teslamate-teslamate-1  | 2024-02-02 16:45:27.010 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (344.893 ms)
teslamate-teslamate-1  | 2024-02-02 16:45:27.010 [info] Refreshed api tokens
teslamate-teslamate-1  | 2024-02-02 16:45:27.016 [info] Scheduling token refresh in 6 h
teslamate-teslamate-1  | 2024-02-02 16:45:27.019 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
teslamate-teslamate-1  | 2024-02-02 16:45:27.020 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate-teslamate-1  | 2024-02-02 16:45:27.152 [info] GET https://owner-api.teslamotors.com/api/1/vehicles -> 412 (131.542 ms)
teslamate-teslamate-1  | 2024-02-02 16:45:27.152 [warning] TeslaApi.Error / %{"error" => "Endpoint is only available on fleetapi. Visit https://developer.tesla.com/docs for more info", "error_description" => "", "response" => nil}
teslamate-teslamate-1  | 2024-02-02 16:45:27.152 [warning] Could not get vehicles: :unknown

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

v1.28.3

@olexs olexs changed the title Release 1.28.3 seemingly not correctly pushed as ARM image Release 1.28.3 seemingly not correctly pushed as arm64 image Feb 2, 2024
@olexs
Copy link
Contributor Author

olexs commented Feb 2, 2024

Nevermind, this was a local issue with Docker and Compose doing weird stuff and not re-creating containers properly. Build is fine, I'm an idiot.

@olexs olexs closed this as completed Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant