Describe the bug
My project is a bit unusual : I'am trying to run redroid container in android AOSP (BTW i'am newbee to Redroid)
For now, I've Cuttlefish Android 14 running k3s fine (no Docker only Rancher stuff) (every kernel specific flags have been setted up)
As Android has already binder natively, do you think that redroid is able to use it ?
So far after many tries the /init can't start. Missing debug logs to identify why ...
Android is able to create separated binder with binderfs, is it a way that can be done ?
Here after my tests.
BTW Redroid is running fine on my k3s cluster on my Ubuntu 22.04 with kernel binder module.
Thanks for any help.
V.
Here is my test :
apiVersion: apps/v1
kind: StatefulSet
#kind: Deployment
metadata:
name: redroid
labels:
app: redroid
spec:
replicas: 1
selector:
matchLabels:
app: redroid
template:
metadata:
labels:
app: redroid
spec:
containers:
- name: redroid
image: redroid/redroid:14.0.0_64only-latest
# command: ["/bin/sleep"]
# args: ["3000"]
readinessProbe:
exec:
command:
- /system/bin/sh
- -c
- test "1" = "`/system/bin/getprop sys.boot_completed`"
initialDelaySeconds: 5
command: ["/init"]
args: ["androidboot.hardware=redroid"]
securityContext:
privileged: true
allowPrivilegeEscalation: true
volumeMounts:
- name: apex
mountPath: /apex
- name: linkerconfig
mountPath: /linkerconfig
- name: hwbinder
mountPath: /dev/hwbinder
- name: binder
mountPath: /dev/binder
- name: logcat
mountPath: /dev/socket/logdw
- name: binderfs
mountPath: /dev/binderfs
- name: properties
mountPath: /dev/__properties__
- name: data
mountPath: /data
- name: sys
mountPath: /sys
volumes:
- name: sys
hostPath:
path: /sys
- name: apex
hostPath:
path: /apex
- name: system
hostPath:
path: /system
- name: linkerconfig
hostPath:
path: /linkerconfig
- name: hwbinder
hostPath:
path: /dev/hwbinder2
- name: binder
hostPath:
path: /dev/binder2
- name: logcat
hostPath:
path: /dev/socket/logdw
- name: binderfs
hostPath:
path: /dev/binderfs2
- name: properties
hostPath:
path: /dev/__properties__
- name: proxy
hostPath:
path: /dev/socket/dnsproxyd
- name: data
emptyDir: {}
Describe the bug
My project is a bit unusual : I'am trying to run redroid container in android AOSP (BTW i'am newbee to Redroid)
For now, I've Cuttlefish Android 14 running k3s fine (no Docker only Rancher stuff) (every kernel specific flags have been setted up)
As Android has already binder natively, do you think that redroid is able to use it ?
So far after many tries the /init can't start. Missing debug logs to identify why ...
Android is able to create separated binder with binderfs, is it a way that can be done ?
Here after my tests.
BTW Redroid is running fine on my k3s cluster on my Ubuntu 22.04 with kernel binder module.
Thanks for any help.
V.
Here is my test :