Document ARM board incompatibility #25
Closed
opened 2020-10-16 16:45:05 +00:00 by decentral1se
·
4 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
No labels
documentation
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#25
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As I've found out doing some installs, we need to check if the images being provided from the projects support ARM based builds. An example of this is https://hub.docker.com/_/traefik?tab=tags. An example of a project not doing it Keycloak (although there are community images).
Then we need to take into consideration, ARM v6/7/8 compat.
e.g. https://hub.docker.com/r/459below/mariadb-armv7/tags
Also 32/64 bit archs! This one works for 3b+:
Problematically, these other images don’t always support
_FILEconventions :(I think overall point for now is that "no, we don't support ARM" because it would involve some serious extra resources to build up a reliable pipeline of builds which we just can't handle right now.
After speaking with some SBC people, it seems like a better idea to stick with boards that do x86 arch so you don't run into this issue. So, the original idea to get https://www.hardkernel.com/shop/odroid-h2plus/ seems to be a good one.
I'll leave this open so we can document this whenever we get public docs.
ARM board compatibilityto Document ARM board incompatibilityMaybe we can add a column for ARM support to the Coop Cloud app list tracker document? Maybe not something for the initial release tho - in which case we should update the "from a Raspberry Pi" language...