Have a look at https://anbox-cloud.io/docs/howto/application/create and https://anbox-cloud.io/docs/ref/application-manifest
tried the things but
Anbox stream failed Error: connector failed to connect: session is not active
geeting this error on
amc application show cf4j8t3hab0noa9h0fo0
id: cf4j8t3hab0noa9h0fo0
name: rise
status: ready
published: true
immutable: false
inhibit-auto-updates: false
tags: []
parent-image: bionic:android12:arm64
abi: armeabi-v7a
config:
instance-type: a2.3
boot-package: com.lilithgame.roc.gp
versions:
0:
image: jammy:android13:arm64 (version 0)
published: true
status: active
boot-activity: com.lilithgame.roc.gp
required-permissions:
- '*'
extra-data: {}
video-encoder: software
watchdog:
disabled: false
allowed-packages:
- com.android.settings
services:
- port: 5559
protocols:
- tcp
expose: false
name: adb
1:
image: jammy:android13:arm64 (version 0)
published: false
status: initializing
boot-activity: com.lilithgame.roc.gp
required-permissions:
- '*'
extra-data: {}
video-encoder: software
watchdog:
disabled: false
allowed-packages:
- com.android.settings
services:
- port: 5559
protocols:
- tcp
expose: false
name: adb
resources:
memory: 8GB
disk-size: 15GB
on amc show
manifest file
name: rise
instance-type: a4.3
resources:
memory: 8GB
disk-size: 15GB
video-encoder: software
required-permissions: ['*']
boot-activity: com.lilithgame.roc.gp
watchdog:
disabled: false
allowed-packages:
- com.android.settings
services:
- name: adb
port: 5559
protocols: [tcp]
expose: false
i think i am going blindy or is this the way to install the app? @morphis
@rijalboy I think you can minimize the manifest.yaml
a bit and that should also help you to get better started. The following should work:
$ cat manifest.yaml
name: rise
instance-type: a4.3
resources:
memory: 8GB
disk-size: 15GB
required-permissions: ['*']
watchdog:
disabled: false
services:
- name: adb
port: 5559
protocols: [tcp]
expose: false
$ ls -1
manifest.yaml
app.apk
$ amc application create . --timeout=10m
If it does not, can you provide the system.log
from the failed container?