Docker container not starting on arm64

[sametjan]

I'm trying to get this image running on my QNAP server, but whenever I try to start the container all I get is standard_init_linux.go:185: exec user process caused "exec format error"

From my docker-compose file:

  organizr:
    image: organizr/organizr:latest
    container_name: organizr
    restart: always
    ports:
      - "80:80"
    volumes:
      -<path>:/config
    env_file:
      - ./shared.env

I've tried both the latest and arm64 tags, but still get the same error in my log.

[Roxedus]

Whats the actual CPU arch on that QNAP? uname -a

[sametjan]

Linux HomeNAS 4.2.8 #2 SMP Sat Oct 24 09:15:05 CST 2020 aarch64 GNU/Linux

[Roxedus]

I spotted some inconsistencies in the manifest, I have now redone that part of the build-process. Does it still behave like this on the latest image?

[sametjan]

Yeah, I'm still getting the same message on the latest image.

[tronyx]

Wait, what version of Docker is installed? docker -v

[sametjan]

Docker version 17.09.1-ce, build 0bbe3ac

[tronyx]

And what version of compose do you have specified at the top of your docker-compose.yml file?

[sametjan]

3.6

[tronyx]

That could be it. Can you try creating a separate compose file in another directory for just the Organizr container and setting the version first to 3.4 and, if that doesn't work, try 2.4? Compose 3.6 has a requirement of Docker 18.02.0+.

[Roxedus]

What about the new non-manifested build? organizr/organizr:linux-arm64

[sametjan]

Tried 3 and 2.4, using organizr/organizr:linux-arm64 and still no luck.

[sametjan]

I finally got a working version. Cloned this repo, and had my docker-compose build the image locally, setting the BASE_IMAGE to organizr/base:latest.

  organizr:
    build:
      context: <path>docker-organizr
      args:
        BASE_IMAGE: organizr/base:latest
    container_name: organizr
    restart: always
    ports:
      - "80:80"
    volumes:
      - <path>:/config
    env_file:
      - ./shared.env
    environment:
      fpm: "true"
      branch: "v2-master"

[tronyx]

Glad that you were able to get it working, albeit needing to be a roundabout way. This seems like an odd edge case, but if you have any additional information that you were able to figure out, please let us know.

[telefax]

Same root cause as #13 ?