-
Notifications
You must be signed in to change notification settings - Fork 74
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
docker-adb for STF as device provider on Odroid XU4 #11
Comments
I would suggest using whatever is easiest with your distro. There’s no official build for arm and most package managers have an ancient version. The one on Alpine Linux is what I’ve used in the past but it is also relatively out of date. Arch Linux also has an out of date package but they’ve worked well enough. You could also try qemu. |
Alright, thanks fo the quick answer! I would like to try to port your container to ARM somehow... do you have any hints for me on that? It seems to me, that the android toolchain your container is downloading from google, is kinda generic, do you think it would suffice, if we replace the |
You'd need to change everything and use qemu to run the binary, or use an unofficial outdated build. |
Okay, just to give you an update on this... I managed to build a Docker container on basis of Archlinux and then installing If this issue is solved by this from your point of view, we can close the issue now. |
Hey, @sorccu
I am trying to get stf running as a device provider on an Odroid XU4 running Arch Linux for a day now and couldn't get this working...
You said, that your XU4 is running smoothely here, so I assume you got your ADB container working on your XU4, but how did you handle this?
When I start your container, I get the error
standard_init_linux.go:195: exec user process caused "exec format error"
.Did you stumble upon this error before?
Research on the net shows, that it's either a architecture error or encoding... But I couldn't figure out what the actual problem is here...
I also tried building the container on the machine, but this didn't work either. When I start this, the 'adb' command throws the error from above...
Do you have any hints on that?
The text was updated successfully, but these errors were encountered: