constellation/nix/container/vpn/strongswan.sh

#!/bin/sh

set -eux

mkdir -p /var/run
export SWANCTL_DIR=/etc/swanctl

# The charon binary is not included in the PATH generated by writeShellCommand, find it manually.
charon="$(dirname "$(readlink -f "$(command -v charon-systemd)")")/../libexec/ipsec/charon"

"${charon}" &

while ! swanctl --stats > /dev/null 2> /dev/null; do
  sleep 1
done
swanctl --load-all

wait
docs: add Helm chart for VPN connectivity (#2577) Co-authored-by: 3u13r <lc@edgeless.systems> 2023-11-22 15:08:11 +01:00			`#!/bin/sh`

vpn: ship our own container image (#2909) * vpn: ship our own container image The container image used in the VPN chart should be reproducible and stable. We're sticking close to the original nixery.dev version by building the image with nix ourselves, and then publishing the single layer from the result with Bazel OCI rules. The resulting image should be handled similar to s3proxy: it's built as a part of the Constellation release process and then consumed from a Helm chart in our registry. Co-authored-by: Malte Poll <1780588+malt3@users.noreply.github.com> 2024-02-15 13:08:27 +01:00			`set -eux`

			`mkdir -p /var/run`
			`export SWANCTL_DIR=/etc/swanctl`

			`# The charon binary is not included in the PATH generated by writeShellCommand, find it manually.`
docs: add Helm chart for VPN connectivity (#2577) Co-authored-by: 3u13r <lc@edgeless.systems> 2023-11-22 15:08:11 +01:00			`charon="$(dirname "$(readlink -f "$(command -v charon-systemd)")")/../libexec/ipsec/charon"`

			`"${charon}" &`

			`while ! swanctl --stats > /dev/null 2> /dev/null; do`
			`sleep 1`
			`done`
			`swanctl --load-all`

			`wait`