Running container through nebula is slow

[para1131]

Expected/Wanted Behavior

I expected container run as fast as i run it manually on the system. i dont mean its download time from repository to my device but I mean process of running container with "docker run" command that will be taken place by nebula-worker after downloading the docker image. actually running container and starting dbus service on container take longer time than the time the container is run manully with "docker run" command and not from nebula-worker.

Actual Behavior

when worker tries to run container it take longer time to start dbus service. around a minute and a half. most bottle neck is running dbus service. but when I build image and run container on the same system (pc) then it boot and start fast without problem.

Steps to Reproduce the Problem

1.update nebula db with new container. wait for worker to download it and run it
or
2. restart the system or docker service and wait the container to restart.

Specifications

Docker image or container uses --privileged mode to enable Bluetooth access. startup script run dbus service and run bluetoothd with -C mode. base os is ubuntu with only java and bluez installed on it.

[naorlivne]

If you build the image on the machine then it's already locally cached & doesn't have to be downloaded, if you run it via nebula then the image has to first be downloaded which could account for the extra time your seeing, trying building an image, pushing it to docker hub then on a fresh machine run it so it will be forced to first download the image before running it, this should give a better time comparison of the two