Thank you for the quick response. The goal of my evaluation is to understand what Celadon
is, how easy to rump-up and overall quality of the release (test coverage, etc). I would
expect some work related to Android on Intel, thus trying to be prepared )
Unfortunately, I still have a trouble with running android docker container.
I’ve managed to find Nuc6i3 to try installation on a bare metal configuration. In addition
to this I’ve upgraded kernel to 5.4 on my existing environment.
So basically I have Ubuntu 18.04 + 5.4 kernel configuration on both:
* Ubuntu virtual machine under Vmware hypervisor
* bare Nuc6i3 with installed ubuntu
In both cases android container exits with 0 return code.
docker log contains the following
$ docker logs android0
remount /system to RW
remount /system to RO
CFC is not critical for the moment and it’s just a one more sign that everything is
As for the Android UI I’d love to have it accessible remotely over vnc connected to host
running Android docker container.
Would Virtual Machine (CIV) configuration in my case be better option than docker (CIC)
From: "Marathe, Yogesh" <yogesh.marathe(a)intel.com>
Date: Tuesday, July 21, 2020 at 12:34
To: Volodymyr Shevchenko <VShevchenko(a)lohika.com>, "celadon(a)lists.01.org"
Subject: RE: Celadon: issues with running in docker container
CIC will work on NUC + Ubuntu 18.04 + 5.4 kernel. There is no intermediate VM or different
host OS expected here. Ubuntu 20.04 support is work in progress, thus none of the CiC
releases so far have been tried with 20.04 (FYI.. latest -
Are you running Ubuntu inside a VM? That’s another variable and would need work on GPU
& display side (on CFC) to work in context of vmware. If you can explain the use case
under evaluation, may be someone can pitch-in with more recommendations. Looks like, you
need Android UI while Android is in container. And this running on a server, so is the UI
expected for local display or a remote display in that case?
Great to hear that you were able to fix couple of issues and proceed with 20.04 but to
reduce unknowns, I suggest you stay on Ubuntu 18.04 until Celadon supports 20.04. Please
feel free to raise PRs if you want changes to be merged.
From: Volodymyr Shevchenko <VShevchenko(a)lohika.com>
Sent: Tuesday, July 21, 2020 2:09 PM
Celadon] Celadon: issues with running in docker container
I’ve been running some evaluation of Celadon Android and fighting with running CIC
configuration for three days already. My main goal for the moment is to install Caledon in
CIC mode and run some tests against it to make sure I’m proceeding in a right direction.
I’ve managed to build sources from three branches but failed to run Android docker
I’ll really appreciate it if you give me the hint in what direction I need to move and
what requirements to run CIC configuration successfully on non NUC platforms.
Bellow you may find more details on that.
Summary on configuration and environment
1. PMR0 March-31-2020 release. Command: $ repo init -u
-b celadon/p/mr0/2020q1 -m cic
2. latest development CiC source code from the master. Command: $ init -u
-b celadon/p/mr0/master -m cic
3. Android P branch. Command: $ repo init -u
-b celadon/p/mr0/master -m cic - but I’m
not sure where it’s relevant
Main sources of information:
1. Run Celadon in a Docker*
2. Build Celadon in Container with Android
* Trusty and SELinux are disabled
1. Ubuntu 18.04.4 LTS
2. Ubuntu 20.04 LTS
Host OS HW environment:
* I’ve got a chance to run them on HPE ProLiant DL380 Gen10 server on Intel Xeon
Silver 4210 CPU under Vmware ESXi 7.0 hypervison
All branches have been successfully built and installed on both platforms with some minor
issues on Ubuntu 20. Then I failed to run docker containers with Android generated from
first and second source branches. Being started they simply exited with 0 return code
without any error message.
As for Android P I managed to run it but had a trouble with CFC , which crashes at
Thus, I have no access to Android GUI and tried to get access over adb (from toolset
generated during the build). Adb is successfully connected to port 5555 but reports
“emulator-5554 offline” for attached devices.
When shelling to container, I can’t check settings as settings cmd fails with the message
“cmd: Can't find service: settings. I would think this is a sign that something could
be wrong with image.
Thank you for any assistance,