-
-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support ARM & ARM64 architectures #38
Comments
I will add an arm build to the v2 branch 👍 |
Any updates on this? In the meantime I've been able to use the pusher/oauth2_proxy since they do provide an ARM build, but I'm having trouble getting it to work with Traefik v2. |
Until this is done you can build yourself an arm image by simply modifying the Dockerfile. If you put |
I've added the Dockerfiles but just need to tweak the builds on docker hub, then I'll try to create a manifest :) |
Last time I checked this wasn't possible on Docker Hub. Maybe it is on Cloud? |
Are you building locally or directly via Docker Hub? I read on another image that ARM variants can be built on x86_64 hardware using |
So this is stuck as it's not completely obvious how to actually get these built on docker hub....I've found a few examples using qemu, but I don't have a readily available arm setup to test this on - if someone has experience with this and/or an existing environment they can test it in, I would hugely appreciate a PR to get this working! |
My suggestion would be building it on travis.
I am not 100% percent certain I extracted the lines correctly from my old script. If you want you can look at the commit where I removed it from my docker images and later replaced it with docker buildx. SuperSandro2000/docker-images@6c274c2 Let me know if this is what you want or if you want to use the newer buildx approach which is way nicer but requires a local docker registry if you don't want to push tests to the official repository. |
@thomseddon just tried your dockerfile on ARM (rasp4) and it returned a non-zero code. EDIT: NVM i used the tag 2.1-arm , golden |
@julien-vu Could You please provide the docker build command You used? I still get the non-zero return code when building and can't figure out how to fix it.
|
@Sigi-cz it looks like you're pulling v0.1.1, but you will want to pull 2 or 2.1 👍 |
@thomseddon I know, but I'm not familiar enough with docker to figure out how to pull the latest commit.
But I got it working in the end. I downloaded the zip, unpacked and ran this:
Maybe You could add little 'how to compile for arm' into the Readme? |
I'm happy to try and set something up to automated this - I've got a bunch of 32bit Raspbians here. You can also try docker buildx |
For Docker Swarm mode this doesn't work correctly. In spite of the Assuming their image relates to #112 A direct
But deploying a stack like: version: '3.4'
services:
fw-auth:
image: thomseddon/traefik-forward-auth:2-arm
command: --help
deploy:
mode: global Creates a task similar to this: Note: [
{
...
"Spec": {
"ContainerSpec": {
"Image": "thomseddon/traefik-forward-auth:2-arm@sha256:c633d20c76c64b4bcdfce5f6c274c00a4fe1efe092348801a560c43c4c1415af",
"Labels": {
"com.docker.stack.namespace": "fwa"
},
"Args": [
"--help"
],
"Privileges": {
"CredentialSpec": null,
"SELinuxContext": null
}
},
"Resources": {},
"Placement": {
"Platforms": [
{
"Architecture": "amd64",
"OS": "linux"
}
]
},
"Networks": [
{
"Target": "45aukoqbi64nhg1tepayn0vc6",
"Aliases": [
"fw-auth"
]
}
],
"ForceUpdate": 0
},
"ServiceID": "xzz2j07wceuynam080ksba87q",
"NodeID": "r7lspnr6dqp5715gzpx56y27v",
"Status": {
"Timestamp": "2020-08-16T19:40:49.0845814Z",
"State": "pending",
"Message": "unsupported platform on 1 node",
"ContainerStatus": {},
"PortStatus": {}
},
...
}
] |
@Beanow Docker Hub can't do manifests easily. If the Image building would be done on some other CI this would be easily possible. |
Just switched to RPI4 and getting this error - is there a workaround? |
Probably building the image yourself for that platform? |
as per title
kindly add support for arm and arm64
The text was updated successfully, but these errors were encountered: