As in title. As I know Android Studio need glibc so I need to use container but how about emulation in container? Is it possible? I have x86_64 CPU.
As in title. As I know Android Studio need glibc so I need to use container but how about emulation in container? Is it possible? I have x86_64 CPU.
8 Comments
just_another_person@lemmy.world · 8 pts · 173d
I'm confused by your question. Why would you need a container for this? There are other packages downloads for Android Studio. Container would be the most convoluted way of running it.
chrash0@lemmy.world · 3 pts · 173d
really? i mean, people have done it for friggin vanilla ass Node.js servers. Android projects can have weird dependencies that a container might help solve (NDK etc).
i’m not saying that it’s my preferred way to build, but that wasn’t the question.
just_another_person@lemmy.world · 3 pts · 173d
Android Studio isn't just a simple app, nor a single executable, AND it maps out to a bunch of local sockets to your already running host to provide various services. Certainly not going to be easy or stable in a container, especially since they are asking about emulation as well.
chrash0@lemmy.world · 0 pts · 173d
lots of good reasons to spin up containers for development is my point, especially for an embedded system with exotic system dependencies (compared to Node.js, for example).
Home Assistant is a “simple app” that i have to open ports for.
does that mean they have a good reason? maybe not.
just_another_person@lemmy.world · 0 pts · 173d
Did you read that I was saying containers are bad somewhere? You have misread.
mlxdy@lemmy.world · 2 pts · 173d
Where are these packages?
just_another_person@lemmy.world · 7 pts · 173d
Flatpak for one: https://github.com/flathub/com.google.AndroidStudio
nortio@feddit.it · 2 pts · 173d
Yes, it's perfectly usable in a container. I use distrobox and the emulator works just fine