This is what I did! I've now migrated to my own docker-compose files.
Dust0741
I used the owner profile. Idk much about it tbh, I have yet to do more in depth testing as my phone doesn't have displayport functionality so I am a little discouraged to be an early adopter too. I couldn't get SSH setup so typing a lot on the small keyboard wasn't ideal.
I'd check Google/GOS docs for more info for now. I'll bet there'll be a lot in the coming years as fast as usecases
Nipe! Not rooted. In a VM though
Not sure, but if LineageOS supports it, that should be all you need
Early alpha, but yea it's full on Linux in Android. Quite slick
I don't know. I think they are pretty good at managing battery, and have a new setting for maxing it out at 80% charge, but I don't think I'd put it near anything expensive for years on end.
Yea kinda. Android is switching to quarterly releases, so my phone now says "Android 15" but this was QPR2 specifically
Hmm I was messing with its networking. External vpns break stuff on GrapheneOS. Its internal IP was 192.168.0.2, and my network is different.
https://docs.docker.com/engine/install/debian/#install-using-the-repository
That's it lol. To turn on the terminal, it's a developer option for now, and is very alpha, just search for Linux in settings after turning on dev mode
That's Debian in the screenshot
Oh man that'd be super cool. An ARM cluster of androids would be awesome. Battery backups built in!
Not really. I also didn't have much data in them, so I opted to start from scratch. I'd recomend searching for "service docker" to find how to run that thing in dockers compose. Then I make a folder for each thing. In my home directory, I make a new folder. Say fileBrowser. Then inside that I make
docker-compose.yml
and put the compose from the internet (if you find a docker run, you can convert it to compose via sites like composerizer). Then for config volumes I like to specify./
so it goes to the current folder. I.e../filebrowserconfig/settings.json:/settings.json
so that inside the fileBrowser folder we're already in, it has a folder called filebrowserconfig and a file called settings.json. (note that docker tries to make folders, not files. So if the json file doesn't already exist, it'll make a folder named settings.json lol)