-
Notifications
You must be signed in to change notification settings - Fork 386
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
Can't install on Mikrotik ac3 #459
Comments
The Mikotik docs say the hAP ac3 has a "4 core IPQ-4019 716 MHz" processor, which looks to be the Qualcom IPQ-4019. That spec sheet says it's a ARM Cortex A7 which should match ARMv7 I think So the containers we make available should work, but without a detailed log there is little we can do to help here. If it's failing while just pulling the container from the registry then it's not even trying to run it. You will need to talk to MikroTik support to find out how to get some logs and details of exactly where it's failing. |
Thank you, yes I'm going to ask more support on Mikrotik's forum. Thanks for answering quick :) |
I've opened a topic asking support here: |
No, not without any error message or logs |
Hi mates, I've troubles installing this container on Mikrotik ac3, I've used the same procedure I did succesfully on CHR (same RouterOS version 7,16), the package extracts but then keeps extracing and doing nothing, no bytes are written more to USB. I've tries also version 3.1.12 as a friend suggested me since it supports v6 processors, but same result.
What can be wrong here? Unfortunately these is no helpful log.
The main difference between installations is that on CHR I've used disk1, and here usb1, maybe this docker doesn't support installation on an external drive?
A ful discussion with all attempts done can be see here, this friend tols he was able to run it on Mikrotik ac2, that maybe has a v7 processor.
thank you for you kind support!
https://forum.mikrotik.com/viewtopic.php?p=1102316#p1102316
To don't waste time, I would suggest start reading from the last reply
The text was updated successfully, but these errors were encountered: