Docker-transmission-openvpn: Dockerize failing with "Exec format error" in arm64 image

Created on 11 Jul 2020  Â·  15Comments  Â·  Source: haugene/docker-transmission-openvpn

bug help wanted

All 15 comments

Please post config, which example are you referring to?

hmm,seems like there is an issue with dockerize generating settings from template
@haugene looks like dockerize not working ?

Exec format error is an error message that I have seen relating to running on wrong cpu architecture before. Are you sure that you should run arm64 image and not armhf? Can you try latest-armhf instead?

I might have spoke too soon. We build the arm64 image with the same Dockerfile as armhf, but we substitute the base image with a build argument. Looking at the Dockerfile though: https://github.com/haugene/docker-transmission-openvpn/blob/master/Dockerfile.armhf

The Dockerize version seems to be hard coded to armhf. That might be the issue here...
https://github.com/haugene/docker-transmission-openvpn/blob/master/Dockerfile.armhf#L28

But there is no arm64 version of Dockerize 🤔
@Mhmccabe did you try running the latest-armhf instead of latest-arm64?

Ok. Maybe we should look for a possible replacement for dockerize if it doesn't support all the architectures we want to support. Looking a bit around it seems we have many good options, but I would prefer a tool that is as simple as possible and that has a small footprint on the image size as well.

The gettext package has the envsubst program and seems to take only 8 MB. Could be a good option.
I'm leaving for a summer vacation trip tomorrow and won't be able to do anything for a week or so. If you want to submit a PR I'd gladly have a look when I'm back. If not we will follow up later.

Dockerize has no arm64 release, but it does have armhf release. Looking into docker hub, there's no arm based version released for transmission-openvpn. All versions seem to be linux/amd64, even if the tag indicates arm.
Screenshot from 2020-08-18 11-29-49

Is this right? Because it seems that regardless the tag you use you're going to get amd64 arch.

Hmm, no they should be arm images. We're building them on amd64 with the cross-build functionality. Should look into how to tag them differently I guess. Open for suggestions and tips.

I've now merged #1323 into dev and it removes Dockerize and should hopefully fix this issue. Mind that the dev branch is under some larger refactoring these days so there might be other bugs. But if you could test with the dev-arm64 tag that could get us closer.

That means it worked @Mhmccabe?

I Haven’t done a full feature test yet, but it launches now

On 24 Aug 2020, at 7:05 pm, Kristian Haugene notifications@github.com wrote:



That means it worked @Mhmccabehttps://github.com/Mhmccabe?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/haugene/docker-transmission-openvpn/issues/1288#issuecomment-679281014, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJGI6UDNEGUG2NFTXAVRZLSCKTVZANCNFSM4OXODB7Q.

Just as an FYI. We're seeing some other issues with the arm images on the dev branch. Working to fix them though. #1341

This may be moot now, but I was able to solve this problem by cloning dockerize, compiling, copying the aarch64 binary to a directory, and then mounting that directory to /usr/local/bin.

Here's part of my docker-compose.yaml:

  transmission:
    image: haugene/transmission-openvpn:latest-arm64
    container_name: transmission
    restart: always
    ports:
      - "9091:9091"
    cap_add:
      - NET_ADMIN
    volumes:
      - /etc/localtime:/etc/localtime:ro
      -/path/to/aarch64/dockerize/bin/:/usr/local/bin # Arm64 version of dockerize
      # Rest of your volumes
    env_file:
      - docker.env

Huh, so they did have a working release. Oh well, we've stopped using Dockerize at this point and it is merged to master. Pulling the latest should remove that error. But the arm versions might still be a bit broken with the new 3.0 release @sametjan? They're next on the list for some maintenance love.

The only issue I was having with the newer images on arm64 was being unable to connect to UDP trackers, but switching VPN providers from Ivacy to ExpressVPN fixed that.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

pejotll picture pejotll  Â·  4Comments

holger8080 picture holger8080  Â·  4Comments

lorgio picture lorgio  Â·  4Comments

avDownloads picture avDownloads  Â·  4Comments

callahan22 picture callahan22  Â·  4Comments