thingsboard / thingsboard-gateway

Open-source IoT Gateway - integrates devices connected to legacy and third-party systems with ThingsBoard IoT Platform using Modbus, CAN bus, BACnet, BLE, OPC-UA, MQTT, ODBC and REST protocols

Home Page:https://thingsboard.io/docs/iot-gateway/what-is-iot-gateway/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Architecture issue with latest tb-gateway image (3.4.6)

DigitalPals opened this issue · comments

Docker Version: 26.0.0, build 2ae903e

Operating System: Ubuntu 22.04 LTS x86_64

Description:
When running docker compose up with a Docker Compose file, I'm encountering an "exec format error" when attaching to one of the containers. The container exits with code 0 immediately after starting.

Steps to Reproduce:
Create a new directory with a docker-compose.yaml file
Add a service definition like:

services:
  # ThingsBoard IoT Gateway Service Configuration
  tb-gateway:
    image: thingsboard/tb-gateway
    container_name: tb-gateway
    restart: always

Run docker compose up

Expected Behavior:
The container should start successfully and attach without any errors.

Actual Behavior:

Attaching to tb-gateway
myservice  | exec /bin/sh: exec format error
myservice exited with code 0

Additional Context:
The Docker image tb-gateway:latest has an architecture of "amd64"

The host system is x86_64, which should be compatible with amd64 images

This issue does not occur on older tb-gateway version (e.g. 3.4.5)

Let me know if you need any other information to investigate this issue further.

Hi @DigitalPals.
Thank you for your interest in ThingsBoard IoT Gateway.
Your issue was registered, please wait for response from engineer.

IOTGW-186

Hi @DigitalPals,

We have updated images on docker hub, please try now.

Hi @imbeacon, I can confirm it starts now. It keeps saying that there is a new version available though. I double checked with docker image inspect 2523b21371ba it was created today.

[===UPDATE===]

 New version 3.4.6 is available! 

[===UPDATE===]

@DigitalPals
The new version message is another bug: #1355

@samy4sam Thanks, I'll close this issue then.