#!/bin/sh

# to enable debugging via gdb
#exec docker run --rm --cap-add=SYS_PTRACE --security-opt seccomp=unconfined -iv /root/opt:/opt -v /var/hasplm:/var/hasplm -v /etc/hasplm:/etc/hasplm -v /tmp/$1.$2.sock:/tmp/$1.$2.sock:Z -v $APL_CONF/$1/conf:$APL_CONF/$1/conf:ro overcast/vae-$2 "$@" >/tmp/$1.$2.log 2>&1

# another way to start engine via shell bypassing entrypoint. DISADVANTAGE: engine will NOT be the container's PID 1 and will not receive Unix signals (e.g. SIGTERM from docker stop <container>)
#eval "exec docker run --rm -iv /var/hasplm:/var/hasplm -v /etc/hasplm:/etc/hasplm -v /tmp/$1.$2.sock:/tmp/$1.$2.sock:Z -v $APL_CONF/$1/conf:$APL_CONF/$1/conf:ro overcast/vae-$2 bash -c \"uuidd; /opt/vae/$2/bin/vae-engine $@\" >/tmp/$1.$2.log 2>&1"

exec docker run --rm -iv /root/debug:/root/debug -v /var/hasplm:/var/hasplm -v /etc/hasplm:/etc/hasplm -v /tmp/$1.$2.sock:/tmp/$1.$2.sock:Z -v $APL_CONF/$1/conf:$APL_CONF/$1/conf:ro overcast/vae-$2 "$@" >/tmp/$1.$2.log 2>&1
