Skip to content
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

arm32v7-beta image's architecure is amd64 in image metadata #84

Closed
kniskala opened this issue Dec 15, 2017 · 6 comments
Closed

arm32v7-beta image's architecure is amd64 in image metadata #84

kniskala opened this issue Dec 15, 2017 · 6 comments

Comments

@kniskala
Copy link

At least the current unifi:arm32v7-beta image's architecture is amd64 in the image metadata.
It works fine when run on stand-alone container (with docker run or docker-compose up) but noticed that when I tried to setup a swarm and run it as a service it got stuck in pending state as there were no amd64 machines in my swarm.

@jacobalberty
Copy link
Owner

Yes, I believe that is the manifest stuff discussed in https://developer.ibm.com/linuxonpower/2017/07/27/create-multi-architecture-docker-image/

I need to figure out how I am going to integrate the builds of non x86 architectures, the docker hub doesn't directly support them at this time and I'm having to do a cross build using qemu. Does swarm allow you to use a build from repository instead of using an image?

@kniskala
Copy link
Author

Ok, so this is a known issue.

An image built from repository gets deployed successfully.
I of course need to push it to another registry for all the swarm participants to be able to find it.
It would just have been nice to be able to skip the building part myself. :)

Thanks for all your work and effort in getting the unifi stuff dockerized.
Much easier to get that up and running than trying to install it on a fresh raspberry pi, especially after the dropped mongodb support in stretch...

@jacobalberty
Copy link
Owner

I'm working on setting up a build server on a raspberry pi 3 now to push images to the hub, hopefully that will fix the metadata issue for you. I'll close this issue when it gets done (hopefully within the week)

@jpawlowski
Copy link

I could help to use Travis for all platforms.
You may take this as a working example: https://github.com/docker-home-automation-stack/fhem-docker

@samriley
Copy link

Hi, was there any update on this? Just starting a project using a multi-arch k8s cluster. I have an issue at the moment that I'm unable to allow the unifi controller to run on any node and instead have to target it to a specific architecture even though it should work on any node.

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants