Docker Compose gives "no matching manifest for linux/armv7 in the manifest list entries"

Installation
1

I purged all Docker containers on one of the Pi’s (3B+), as I do every few months, did a full upgrade of the system and a reboot. Then I started Zigbee2MQTT, it pulled the Docker container and was up and running. But doing the same thing to Hass gave me that error message,

no matching manifest for linux/armv7 in the manifest list entries

Any idea why this is happening, and what I can do to fix it? I went from Core kicking and screaming when the changes in dependencies got impossible to follow from version to version and took more time than I had.

2

Found the solution myself, but I’ll leave the message as it is, in case anybody else has the problem: The Docker Compose file was too old. Updating the version from 2.1 to 3 and fixing a few other things according to the documentation fixed it.

3

I’m new to docker and home assistant. I have homebridge running an a Raspberry Pi 4 Model B Rev 1.4. I would like to run Home Assistant on this Raspberry Pi as well via docker. I get the same “no matching manifest for linux/arm/v7 in the manifest list entries.”

From your explanation it appears that you said to update the docker-compose.yml file to reference version 3. That is not working for me. Am I missing something? Any assistance would be greatly appreciated.

4

Can it have something to do with Homebridge? I think that is a specially constructed image, right?

5

what kind of solution is that ?
Leave a real solution at least .

6

If you mean the one marked as a solution two posts up, it’s one that worked. And still works.

7

Upgraded to ver 3.0? How? And fixing some other stuff in the documentation? What? Where?

8

There is only one place to upgrade a Docker Compose file, which is what I wrote. The first line. Change:

version: '2.1'

to:

version: '3'

And the documentation is here, I probably should have noted that:

If I remember correctly, the change needed was adding:

    privileged: true