#!/bin/sh
set -eu

# Chromium writes these locks with the container hostname. After a Docker
# recreation, that hostname changes and the persisted profile can no longer
# start until the obsolete locks are removed.
profile=/home/seluser/browser-profile
if [ -d "$profile" ]; then
  rm -f \
    "$profile/SingletonCookie" \
    "$profile/SingletonLock" \
    "$profile/SingletonSocket" \
    "$profile/DevToolsActivePort" \
    "$profile/Default/LOCK"
fi

exec /opt/bin/entry_point.sh "$@"