nonot at all i find very hard in installing apps more than 100MB with does not have obb file
Hey @rijalboy!
Anbox Cloud generally supports APKs for larger size than 100MB.
You can add APKs to applications and then submit them via amc application add. If the APK is going to be significant larger than 100MB you may want to add --timeout=10m to the amc application add command to not let it timeout (the default is 5min).
The web dashboard has currently a limit of 100MB for APKs but that is going to be changed in the upcoming 1.17 release.
Furthermore you can do all kinds of different customization to the Android rootfs by using hooks. See https://anbox-cloud.io/docs/ref/hooks for more details.
Let us know if you have any further questions.
regards,
Simon
also when i run add the app from app dashboard it launches successfully but when i do it from command line i am getting the error on the status. what am i supposed to do for this cause manifest.yaml don’t have proper documentation.
amc application add does not works here my manifest.yaml looks like
name: rise
instance-type: a4.3
watchdog:
disabled: true
dir structure is like
|-rise.apk
|-manifest.yaml
i created app
amc application create . --timeout=20m
not working
i created app
amc application create . --timeout=20m
not working
Can you tell us what error you run into?
Also can you give us a bit more insight into what system you’re running Anbox Cloud on?
when i did amc aaplication ls the app show published: false and status:error and i deleted it i downloaded app from apk pure called rise of kingdoms can you help me on this i can provide you further details @morphis
please help me on this you are my last hope
When your application fails to boostrap you will find a container status error in the amc ls output. Running amc show <container id> will give you more information about why it failed and together with amc show-log <container id> <log name> you can look closer at the logs of the failed container. See https://anbox-cloud.io/docs/howto/container/logs for more details.
It’s likely that the APK failed to install for some reason.
id: cf3vd0fojmog2e66t8i0
name: ams-cf3vd0fojmog2e66t8i0
status: error
node: lxd0
created_at: 2023-01-18 13:39:13 +0000 UTC
application:
id: cf3vbrfojmog2e66t8hg
network:
address: ""
public_address: ""
services: []
stored_logs: []
error_message: 'Failed creating instance from image: Unable to unpack image, run out
of disk space'
config: {}
app_id: cf3vbrfojmog2e66t8hg
app_version: 0
image_id: ""
image_version: 0
got this error but my disk size is large in my machine also when add bomsquad game from dashboard it works well but from cli it shows same error @morphis
after increasing the size i am getting this error again
id: cf40ra7ojmog2djim7j0
name: ams-cf40ra7ojmog2djim7j0
status: error
node: lxd0
created_at: 2023-01-18 15:18:00 +0000 UTC
application:
id: cf40q57ojmog2djim7ig
network:
address: ""
public_address: ""
services: []
stored_logs: []
error_message: 'Failed creating instance from image: Unable to unpack image, run out
of disk space'
config: {}
resources:
memory: 8GB
disk-size: 15GB
app_id: cf40q57ojmog2djim7ig
app_version: 0
image_id: ""
image_version: 0
my manifest.yaml file
name: rise
instance-type: a4.3
resources:
memory: 8GB
disk-size: 15GB
Thanks for the details.
You LXD storage pool seems to be too small. Are you using a separate EBS volume for the LXD storage pool or a on disk volume?
Can you provide the output of sudo zfs list (you may need to run sudo apt install -y zfsutils-linux first)?
NAME USED AVAIL REFER MOUNTPOINT
data 16.1G 1.80G 24K legacy
data/containers 9.33G 1.80G 24K legacy
data/containers/juju-02361d-0 910M 1.80G 1.76G legacy
data/containers/juju-02361d-1 6.46G 1.80G 7.33G legacy
data/containers/juju-02361d-2 1.21G 1.80G 2.17G legacy
data/containers/juju-20764a-0 797M 1.80G 1.65G legacy
data/custom 4.83G 1.80G 24K legacy
data/custom/default_backups 24K 1.80G 24K legacy
data/custom/default_images 4.83G 1.80G 4.83G legacy
data/deleted 120K 1.80G 24K legacy
data/deleted/containers 24K 1.80G 24K legacy
data/deleted/custom 24K 1.80G 24K legacy
data/deleted/images 24K 1.80G 24K legacy
data/deleted/virtual-machines 24K 1.80G 24K legacy
data/images 1.95G 1.80G 24K legacy
data/images/851d46fc056a4a1891de29b32dad2a1fdecebf4961481e2cc0a5c2ee453e49ba 989M 1.80G 989M legacy
data/images/8bf0ce0604c345ba92b6dcfbb16ad625a948cca14f9c1258707b1de6aba42201 1009M 1.80G 1009M legacy
data/virtual-machines 24K 1.80G 24K legacy
juju-zfs 522K 8.23G 24K legacy
juju-zfs/containers 24K 8.23G 24K legacy
juju-zfs/custom 24K 8.23G 24K legacy
juju-zfs/deleted 120K 8.23G 24K legacy
juju-zfs/deleted/containers 24K 8.23G 24K legacy
juju-zfs/deleted/custom 24K 8.23G 24K legacy
juju-zfs/deleted/images 24K 8.23G 24K legacy
juju-zfs/deleted/virtual-machines 24K 8.23G 24K legacy
juju-zfs/images 24K 8.23G 24K legacy
juju-zfs/virtual-machines 24K 8.23G 24K legacy
here are the details of zfs list
So yeah, your storage pool is too small. You have only 1.6GB left.
At initialization time of the appliance you’re being asked whether you want a separate EBS volume to use (recommended) or what the size of the on-disk loopback mounted storage pool should be. The size of a on-disk pool will by default be calculated as a percentage of your root-disk volume. Have a look at https://anbox-cloud.io/docs/howto/install-appliance/aws for how to add the EBS volume. Once added when you create the instance you can select it when running anbox-cloud-appliance init (see https://anbox-cloud.io/docs/howto/install-appliance/finalise).
i have 50 GB and 100GB volume attached to it but i don’t know how come it’s not managining the storage I have destroyed anbox cloud by running anbox-cloud-appliance destroy and rerun that init process to default but could not fix the issue. @morphis
@rijalboy What answers have you given during the initialization? There is specifically a question as follows:
Do you want to use a dedicated block storage device? [default=yes]
What is the path to the block storage device? [default=/dev/nvme1n1]
The first one you must answer with “yes” and for the second one you provide the path to the EBS volume disk node on your EC2 instance, if it is not selected automatically (which may happen if you destroyed a previous installation without a reboot).
yes now installed but give me an error of webrtc lost connection i checked out chrome web rtc internal chrome://webrtc-internals/
i have updated application with
name: rise
instance-type: a4.3
resources:
memory: 8GB
disk-size: 15GB
video-encoder: software
i tried to add required-permissions:['*']
but it show required-permissions:without an apk not allowed
This indicates you have not added an APK to your app. You need to locate the APK as app.apk within the application package, otherwise AMS and Anbox wont find it.
how to do that? cause i don’t know that i have put in dir with the apk file needs to e renamed or from riseofkingdoms.apk to app.apk?