jyapayne/anbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Start bridge as part of the container manager

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

10
scripts/container-manager.sh
View file

@ -29,4 +29,12 @@ chmod 666 /dev/ashmem
# this path. # this path.
mkdir -p $SNAP_COMMON/lxc 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

10
snapcraft.yaml
View file

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