IOTstack running on thin-client PC hardware instead of raspberry pi - image for linux/amd64/v2

[dalklein]

I'm been happily running classicmqtt on a raspberry pi in IOTstack for years now. Thanks very much for creating and sharing classicMQTT!

The raspberry pi hardware is a bit overtaxed so I'm migrating the whole setup to a thin-client running proxmox, with a linux VM acting as a pi.

When starting the stack, it complains about the target of the docker image it downloads, not matching what it's being run on.

✔ classic_mqtt Pulled 1.1s
[+] Running 7/8
✔ Container influxdb Running 0.0s
✔ Container mosquitto Running 0.0s
✔ Container nodered Running 0.0s
✔ Container portainer-ce Running 0.0s
✔ Container python Running 0.0s
✔ Container yasdi2mqtt Running 0.0s
⠋ Container classic_mqtt Recreate 0.0s
✔ Container grafana Running 0.0s
Error response from daemon: image with reference classicdiy/classicmqtt was found but its platform (linux/arm64) does not match the specified platform (linux/amd64/v2)

I guess I need to figure out how to create a classicMQTT docker image for the new (linux/amd64/v2) target platform? Any advice? Possible to add the new platform to the docker hosted image and then it would just work maybe? Docker is yet another of my barely jack of trades, certainly not master of it.

Thanks! Dale

[mcsarge]

Hey Dale, I have this setup exactly running - but I could not use the Docker image either, I have to build it using the docker stuff. I can give you my setup - I am using IOTStack to run the whole thing on one ProxMox LXC of Ubuntu. Here is my section for ClassicMQTT services: classic_mqtt: container_name: classic_mqtt image: classic_mqtt restart: unless-stopped build: ../github/ClassicMQTT/code/Python environment: - LOGLEVEL=DEBUG - CLASSIC=192.168.0.225 - CLASSIC_PORT=502 - CLASSIC_NAME=classic - MQTT_HOST=mosquitto - MQTT_PORT=1883 - MQTT_ROOT=ClassicMQTT - MQTT_USER=ClassicPublisher - MQTT_PASS=ClassicPub123 - AWAKE_PUBLISH_RATE=15 - SNOOZE_PUBLISH_RATE=300 I cannot remember if I have a slightly different version checked out to that directory... I can compare it for you if you want to give it a go. Matt

…

On Mon, Mar 31, 2025 at 3:46 PM dalklein ***@***.***> wrote: I'm been happily running classicmqtt on a raspberry pi in IOTstack for years now. Thanks very much for creating and sharing classicMQTT! The raspberry pi hardware is a bit overtaxed so I'm migrating the whole setup to a thin-client running proxmox, with a linux VM acting as a pi. When starting the stack, it complains about the target of the docker image it downloads, not matching what it's being run on. ✔ classic_mqtt Pulled 1.1s [+] Running 7/8 ✔ Container influxdb Running 0.0s ✔ Container mosquitto Running 0.0s ✔ Container nodered Running 0.0s ✔ Container portainer-ce Running 0.0s ✔ Container python Running 0.0s ✔ Container yasdi2mqtt Running 0.0s ⠋ Container classic_mqtt Recreate 0.0s ✔ Container grafana Running 0.0s Error response from daemon: image with reference classicdiy/classicmqtt was found but its platform (linux/arm64) does not match the specified platform (linux/amd64/v2) I guess I need to figure out how to create a classicMQTT docker image for the new (linux/amd64/v2) target platform? Any advice? Possible to add the new platform to the docker hosted image and then it would just work maybe? Docker is yet another of my barely jack of trades, certainly not master of it. Thanks! Dale — Reply to this email directly, view it on GitHub <#45>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABP3HEAENU7A5MGI25OFMT2XGLSPAVCNFSM6AAAAAB2FDLTO6VHI2DSMVQWIX3LMV43ASLTON2WKOZSHE3DCNBSGA4TINI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: dalklein]*dalklein* created an issue (ClassicDIY/ClassicMQTT#45) <#45> I'm been happily running classicmqtt on a raspberry pi in IOTstack for years now. Thanks very much for creating and sharing classicMQTT! The raspberry pi hardware is a bit overtaxed so I'm migrating the whole setup to a thin-client running proxmox, with a linux VM acting as a pi. When starting the stack, it complains about the target of the docker image it downloads, not matching what it's being run on. ✔ classic_mqtt Pulled 1.1s [+] Running 7/8 ✔ Container influxdb Running 0.0s ✔ Container mosquitto Running 0.0s ✔ Container nodered Running 0.0s ✔ Container portainer-ce Running 0.0s ✔ Container python Running 0.0s ✔ Container yasdi2mqtt Running 0.0s ⠋ Container classic_mqtt Recreate 0.0s ✔ Container grafana Running 0.0s Error response from daemon: image with reference classicdiy/classicmqtt was found but its platform (linux/arm64) does not match the specified platform (linux/amd64/v2) I guess I need to figure out how to create a classicMQTT docker image for the new (linux/amd64/v2) target platform? Any advice? Possible to add the new platform to the docker hosted image and then it would just work maybe? Docker is yet another of my barely jack of trades, certainly not master of it. Thanks! Dale — Reply to this email directly, view it on GitHub <#45>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABP3HEAENU7A5MGI25OFMT2XGLSPAVCNFSM6AAAAAB2FDLTO6VHI2DSMVQWIX3LMV43ASLTON2WKOZSHE3DCNBSGA4TINI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Matt Sargent ***@***.***

[dalklein]

Thanks Matt! I also just got it to work by building docker image locally, with chatGPT pointing the way. Now have data coming in again from my Classic 250!

I think I did the following:

pi@prx-iot:~$ git clone https://github.com/ClassicDIY/ClassicMQTT.git
pi@prx-iot:~$ cd ClassicMQTT/code/Python
pi@prx-iot:~/ClassicMQTT/code/Python$ docker buildx build --platform linux/amd64 -t classicmqtt-amd64 --load .

edit ~/IOTstack/docker-compose.yml section to use new image

  classic_mqtt:
    container_name: classic_mqtt
    image: classicmqtt-amd64:latest             <--------------------this
    restart: unless-stopped
    environment:
    - LOGLEVEL=DEBUG
    - CLASSIC=192.168.15.11
    - CLASSIC_PORT=502
    - CLASSIC_NAME=MNC250CP
    - MQTT_HOST=mosquitto
    - MQTT_PORT=1883
    - MQTT_ROOT=ClassicMQTT
    - MQTT_USER=mqtt_user
    - MQTT_PASS=mqtt_user_pw
    - AWAKE_PUBLISH_RATE=3
    - SNOOZE_PUBLISH_RATE=3
    - WAKE_DURATION=300
    logging:
      driver: "json-file"
      options:
        max-file: "3"  # number of files
        max-size: "1m" # file size

[mcsarge]

Nice! Matt Sargent ***@***.***

…

On Mon, Mar 31, 2025, 4:52 PM dalklein ***@***.***> wrote: Thanks Matt! I also just got it to work by building docker image locally, with chatGPT pointing the way. Now have data coming in again from my Classic 250! I think I did the following: ***@***.***:$ git clone https://github.com/ClassicDIY/ClassicMQTT.git ***@***.***:$ cd ClassicMQTT/code/Python ***@***.***:~/ClassicMQTT/code/Python$ docker buildx build --platform linux/amd64 -t classicmqtt-amd64 --load . edit ~/IOTstack/docker-compose.yml section to use new image classic_mqtt: container_name: classic_mqtt image: classicmqtt-amd64:latest <--------------------this restart: unless-stopped environment: - LOGLEVEL=DEBUG - CLASSIC=192.168.15.11 - CLASSIC_PORT=502 - CLASSIC_NAME=MNC250CP - MQTT_HOST=mosquitto - MQTT_PORT=1883 - MQTT_ROOT=ClassicMQTT - MQTT_USER=mqtt_user - MQTT_PASS=mqtt_user_pw - AWAKE_PUBLISH_RATE=3 - SNOOZE_PUBLISH_RATE=3 - WAKE_DURATION=300 logging: driver: "json-file" options: max-file: "3" # number of files max-size: "1m" # file size — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABP3HC77TGZPY4B43B67UT2XGTHVAVCNFSM6AAAAAB2FDLTO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRXGM3TAOJYGM> . You are receiving this because you commented.Message ID: ***@***.***> [image: dalklein]*dalklein* left a comment (ClassicDIY/ClassicMQTT#45) <#45 (comment)> Thanks Matt! I also just got it to work by building docker image locally, with chatGPT pointing the way. Now have data coming in again from my Classic 250! I think I did the following: ***@***.***:$ git clone https://github.com/ClassicDIY/ClassicMQTT.git ***@***.***:$ cd ClassicMQTT/code/Python ***@***.***:~/ClassicMQTT/code/Python$ docker buildx build --platform linux/amd64 -t classicmqtt-amd64 --load . edit ~/IOTstack/docker-compose.yml section to use new image classic_mqtt: container_name: classic_mqtt image: classicmqtt-amd64:latest <--------------------this restart: unless-stopped environment: - LOGLEVEL=DEBUG - CLASSIC=192.168.15.11 - CLASSIC_PORT=502 - CLASSIC_NAME=MNC250CP - MQTT_HOST=mosquitto - MQTT_PORT=1883 - MQTT_ROOT=ClassicMQTT - MQTT_USER=mqtt_user - MQTT_PASS=mqtt_user_pw - AWAKE_PUBLISH_RATE=3 - SNOOZE_PUBLISH_RATE=3 - WAKE_DURATION=300 logging: driver: "json-file" options: max-file: "3" # number of files max-size: "1m" # file size — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABP3HC77TGZPY4B43B67UT2XGTHVAVCNFSM6AAAAAB2FDLTO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRXGM3TAOJYGM> . You are receiving this because you commented.Message ID: ***@***.***>

[dalklein]

Note to self: compare mcsarge's and my docker-compose sections. I had this confusion with a different container also.

this way, docker-compose will get the source from github on it's own and build the container, which probably works on any target (raspberry arm, or PC amd)
image: classic_mqtt
build: ../github/ClassicMQTT/code/Python

with only the image listed, it needs to be build manually.
image: classicmqtt-amd64:latest