Start bridge as part of the container manager

This commit is contained in:
Simon Fels 2016-12-04 17:16:55 +01:00
commit a86a5847f8
2 changed files with 15 additions and 5 deletions

View file

@ -29,4 +29,12 @@ chmod 666 /dev/ashmem
# this path.
mkdir -p $SNAP_COMMON/lxc
exec $SNAP/usr/sbin/aa-exec -p unconfined -- $SNAP/bin/anbox-wrapper.sh container-manager
# We start the bridge here as long as a oneshot service unit is not
# possible. See snapcraft.yaml for further details.
$SNAP/bin/anbox-bridge.sh start
$SNAP/usr/sbin/aa-exec -p unconfined -- $SNAP/bin/anbox-wrapper.sh container-manager
pid=$!
waitpid $pid
$SNAP/bin/anbox-bridge.sh stop

View file

@ -14,10 +14,12 @@ apps:
container-manager:
command: bin/container-manager.sh
daemon: simple
bridge:
command: bin/anbox-bridge.sh start
stop-command: bin/anbox-bridge.sh stop
daemon: oneshot
# FIXME: a oneshot unit with start/stop commands needs also RemainAfterExit=yes
# but this isn't supported by snapd yet. See LP #1647169 for details.
# bridge:
# command: bin/anbox-bridge.sh start
# stop-command: bin/anbox-bridge.sh stop
# daemon: oneshot
parts:
android-rootfs: