Droidspaces
1.2K subscribers
243 photos
26 videos
31 files
105 links
Download Telegram
Anyone tried running an AI in their container? 👀
🔥1💩1
Please open Telegram to view this post
VIEW IN TELEGRAM
💩1
What CPU architecture does your Android device use?

If you use Droidspaces, please vote! We need to see if anyone uses 32-bit ARM or x86/x86_64 devices, so we know whether to provide rootfs tarballs for them
Anonymous Poll
97%
aarch64 (Modern 64-bit ARM / Most modern phones)
7%
armhf (Old 32-bit ARM)
6%
x86_64 (64-bit PC or Emulator)
1%
x86 (32-bit PC or Emulator)
1💩1
Proof of concept: Custom rootfs repositories support :)
🔥11💩1
Droidspaces
Photo
Testing:
https://t.me/DroidspacesCI/433?single

rootfs.json:
https://github.com/Droidspaces/linuxcontainers-mirror/raw/refs/heads/main/rootfs.json
2💩1
The first YouTube video covering Droidspaces is out!

He is even running Android Studio directly on Android 🗿

The video also showcases running Jellyfin, Immich, Docker, Nextcloud, and Home Assistant.

It's incredible to see the community staying by our side, no matter what challenges we face. We are growing! Almost 1K stars 🥳

https://youtu.be/gPUXC-xwyIQ?si=CskAV0DnUf4U-DbI
🔥26🗿41💩1
We are happy to announce that we passed our 1,000-stars goal within 3 months.

Thank you to everyone who supported us and contributed to our project ❤️
231🔥5💩1
DroidSpaces 📱

A lightweight, LXC-like container runtime for Android and Linux. Run full Linux distributions natively with zero performance penalty

ℹ️ Overview :
- Real native Linux containers on Android with 0 virtualization overhead
- Boot time 150ms to 750ms with full systemd as PID 1, nothing else on Android comes close
- Run systemd, OpenRC, runit, s6, SysVinit, whatever init system you want, natively
- Truly unkillable. Survives 25+ days, immune to Android's battery killers and LMK
- Zero data loss even after app uninstallation, containers and daemons keep running, your data lives in /data/local/Droidspaces, independent of everything
- Starts before any user app, even before you unlock your phone while its encrypted, via native init.rc/service.d integration
- Run Docker, LXC, Podman inside Droidspaces, nested containers work natively on ALL kernels
- Real hardware access out of the box, full udev/systemd-udevd support like a real Linux PC
- Out of the box Qualcomm Turnip/Virgl GPU acceleration and Termux:X11 support, single toggle
- Arch, Alpine, Fedora, Ubuntu, Debian, OpenWRT, you name it, Droidspaces runs it
- Full namespace isolation: PID, MNT, IPC, UTS, Cgroup, completely separate from Android
- NAT/Host/None networking with port forwarding, TCP and UDP, works out of the box, no manual bridge setup
- Volatile/ephemeral containers via OverlayFS, all changes in RAM, gone on exit
- Portable rootfs.img support with loop mount, fsck, and SELinux hardening
- 0 dependencies. The entire runtime is a single ~400KB static musl binary
- Works on kernels as old as 3.10, supports aarch64, armhf, x86_64, x86 and riscv64
- Beautiful Android app to manage unlimited containers with full GUI control
- Custom bind mounts, multi-DNS, per-container cgroup hierarchies, and dozens more features


🔎: GitHub
👀: Preview
🖥: Codebase
💎: #Android #Linux #Containers #Kotlin

Join us: @Androbusket 👈
🗿7🔥2💩1
Droidspaces has been falsely detected as malware on VirusTotal and OnePlus devices' built-in security scanning tools.

I want to clarify that this is a false positive. The issue has been 99% resolved after changing ~20 lines of code in the codebase.

The new CI builds will give you absolutely 0 false positives on OnePlus devices.

Droidspaces is an open-source project, and everything is fully transparent.

We follow strict rules to protect the codebase from malicious contributors and attackers.

Anyone spreading misinformation or blaming the developers will be instantly fedbanned/gbanned without any further discussion.
🗿205💩1🤣1
As a rooted Android user, what do you prefer Droidspaces to be?
Final Results
17%
Sandboxed environment
83%
Freedom to do whatever you like
🗿31💩1
Next version of Droidspaces is on the way!

But, it totally depends on how stable this CI variant is:

https://t.me/DroidspacesCI/455?single

So, testing and reporting any issues if they exist is appreciated 🤝
👍10💩1
Droidspaces v6.2.5 has been released! 🥳

What's new?

- app: implement rootfs repository browser and download manager for rootfs tarballs with custom repository support
- mount: add :ro flag support for read-only bind mounts
- post_extract_fixes: restrict dhcpcd to NAT mode and whitelist eth interfaces to prevent Android network interference
- fix: prevent Linux /dev breakage by restricting device pruning to Android environments
- fix: add hostname sanitization and validation for container configuration menu
- fix: cancel terminal session notification upon service termination or empty session state
- seccomp: truly skip all filters when noseccomp is active
- Android: fix icon cache poisoning and stale state after container poweroff
- fix: log: persist container logging across pivot_root isolation
- build: fix all hardened-debug compiler warnings
- daemon: add mid-run log rotation for droidspacesd.log
- ds_dhcp: fix cross-container DHCP leaks with ifindex and direction filtering
- mount: unify masking as self-bind+RO, drop unused shared mask-dir tmpfs
- fix: declare BootReceiver to satisfy RECEIVE_BOOT_COMPLETED permission
- build: reduce R8 obfuscation to lower AV heuristic score
- post_extract_fixes: generate and set machine-id to prevent systemd deadlocks on Fedora 44
- post_extract_fixes: remove problematic iptables service files
- seccomp: drop mknod/mknodat device blocking


and misc. UI improvements and bug fixes.

Full Changelog and Downloads:

https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.2.5

@Droidspaces
210💩1
Droidspaces
app: implement rootfs repository browser and download manager for rootfs tarballs with custom repository support
If you need to learn more about the newly added rootfs repository feature and add the LXC rootfs tarballs repository to the app, please refer to this part of the documentation:

https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Usage-Android-App.md#rootfs-repository
🗿6💩1
If you were concerned about Duck Detector detecting Droidspaces, you don't have to be anymore.

Both the droidspacesd SELinux issue and the /dev/pts/1-7 ROOT PTY issues are fully fixed now in the latest CI.

https://t.me/DroidspacesCI/473?single

(Have to reboot the phone after the installation)

These were actual bugs on our side. Fixing them eventually fixed the Duck Detector detection.

Banking people happy now?
🗿8🔥41💩1
30 days of uptime goal is completed!

This proves we are truly unstoppable 💪🏽
🔥112🗿2💩1
Droidspaces
This is just an announcement for people who use 69 different root-hiding modules and 1 billion root detectors to hide root. Root, then install 1 billion pieces of duct tape on top of it to hide what you did, just to use 1 root tool? If you know me, I'm strongly…
Guys,

I'm being honest,

I don't want to bring back the idea of hiding root into my own project.

It's such a pointless idea.

People are literally advising me to hide root. But why? Why would I add duct tape to our project?

It's not the point of containerization.

As I always say, if you want to use banking apps while using Droidspaces,

Either stop using Droidspaces OR your banking app.

This problem exists even in your chroot, Docker container, or LXC.

This is how Linux works.

As we are maturing, I don't want to add the poisonous Android-related idea of hiding root to our code.

If I add such things, our group fills with root detector screenshots, and it really pollutes the community.

Droidspaces is a power user's tool.

Not made for ordinary people who depend on banking apps.

I'm following LXC/Docker/FSF's roots, not the ideas of poisonous devs in the rooting community.

So, stop using Droidspaces if you need banking apps. Use PRoot or QEMU. They do not run as root. They won't give you scary warnings in your detector.
28🔥6👏4
This media is not supported in your browser
VIEW IN TELEGRAM
Proof of Concept: 1-click Termux:X11 support

Think of it like this:


1. You toggle Termux:X11 and add the DISPLAY=:0 environment variable.

2. You start the app.

3. You open the Termux:X11 app.

4. Your desktop is right in front of your eyes 🗿

- 0 Termux usage
- 0 Command knowledge needed.

It just works.

This is still in the testing stages. Sometimes it works and sometimes it doesn’t due to SELinux. After some testing, we will merge it into the dev branch.
25🔥5