Hi, I am getting a timeout error when I deploy my application to fleet with device type “raspberry-pi2” on our openbalena server.
[Build] gateway Step 1/7 : FROM balenalib/raspberry-pi2-debian-openjdk:11-bullseye
[Build] gateway —> f7233e87ef2e
[Build] gateway Step 2/7 : EXPOSE 8080
[Build] gateway —> Using cache
[Build] gateway —> 7ab8013cdc70
[Build] gateway Step 3/7 : RUN pwd
[Build] gateway —> Using cache
[Build] gateway —> 4837c503d639
[Build] gateway Step 4/7 : RUN mkdir /opt/app
[Build] gateway —> Using cache
[Build] gateway —> 090edaf86e08
[Build] gateway Step 5/7 : COPY target/*.jar /opt/app/gateway.jar
[Build] gateway —> Using cache
[Build] gateway —> df99d38c95b9
[Build] gateway Step 6/7 : WORKDIR /data/zstech-gateway/
[Build] gateway —> Using cache
[Build] gateway —> 9ccff5f11bc4
[Build] gateway Step 7/7 : CMD [“java”, “-jar”, “/opt/app/gateway.jar”]
[Build] gateway —> Using cache
[Build] gateway —> e68f5789ccc0
[Build] gateway Successfully built e68f5789ccc0
[Build] gateway Successfully tagged ch.zstech.gateway_gateway:latest
[Build] gateway Image size: 508.38 MB
[Build] Built 1 service in 0:08
[Info] Creating release…
[Info] Saving release…
[Error] Deploy failed
(HTTP code 500) server error - i/o timeout
Deploying to a fleet with other device type, e.g. revpi-core-3 works as expected.
The server has version 3.6.0 installed and the CLI version 13.5.3
But when I create the fleet with device type “raspberrypi2” (without dash), everything works like expected. Even the device, I have to configure with the device type “raspberrypi2”.
Is there a reason for that missmatch in device type names and is it documented somewhere?