# Docker and/or Kubernetes official support

**URL:** <https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431>\
**Category:** Pritunl VPN\
**Created:** [October 3, 2022, 4:54pm UTC](https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431 "2022-10-03T16:54:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![iqbalaydrus](https://forum.pritunl.com/user_avatar/forum.pritunl.com/iqbalaydrus/32/163_2.png) [@iqbalaydrus](https://forum.pritunl.com/u/iqbalaydrus)\
**Post date:** [October 3, 2022, 4:54pm UTC](https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431/1 "2022-10-03T16:54:55Z")

</div>

Hello,

Our company manages a few kubernetes cluster, and pritunl is a great choice in managing them. Creating pritunl server is quite easy since there are some unofficial images available. But we cannot seem to find a way for setting up pritunl-client and pritunl-link in docker/kubernetes. Our last resort is to use vanilla openvpn client and use iroute there.

Do you have any plans on better supporting containerized platform?

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [October 3, 2022, 10:38pm UTC](https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431/2 "2022-10-03T22:38:08Z")

</div>

The same configuration commands should work in a Docker container after the configuration is done run the command `pritunl-link start`

---

<div class="post-metadata">

**Author:** ![iqbalaydrus](https://forum.pritunl.com/user_avatar/forum.pritunl.com/iqbalaydrus/32/163_2.png) [@iqbalaydrus](https://forum.pritunl.com/u/iqbalaydrus)\
**Post date:** [October 4, 2022, 3:03am UTC](https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431/3 "2022-10-04T03:03:19Z")

</div>

Ok, I’ll tinker more about pritunl-link, I only tried once. What about the pritunl-client? I tried the documented commands, and it didn’t work. Or maybe it’s expected to not work in a container?

```auto
root@eceed50acc65:/# pritunl-client add pritunl://xxxxx
panic: auth: Failed to auth key
open /var/run/pritunl.auth: no such file or directory
ORIGINAL STACK TRACE:
github.com/pritunl/pritunl-client-electron/cli/service.GetAuthKey
	/go/src/github.com/pritunl/pritunl-client-electron/cli/service/utils.go:44 +0x6aded6
github.com/pritunl/pritunl-client-electron/cli/sprofile.Import
	/go/src/github.com/pritunl/pritunl-client-electron/cli/sprofile/utils.go:470 +0x6ba827
github.com/pritunl/pritunl-client-electron/cli/sprofile.ImportUri
	/go/src/github.com/pritunl/pritunl-client-electron/cli/sprofile/utils.go:626 +0x6bbaaf

```

And when installing, there was some interesting errors.

```auto
root@eceed50acc65:/# apt-get update && apt-get -y install gnupg ca-certificates && \
    gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 7568D9BB55FF9E5287D586017AE645C0CF8E292A && \
    { gpg --armor --export 7568D9BB55FF9E5287D586017AE645C0CF8E292A > /etc/apt/trusted.gpg.d/pritunl.asc ; } && \
    { echo "deb https://repo.pritunl.com/stable/apt jammy main" > /etc/apt/sources.list.d/pritunl.list ; } && \
    apt-get update && apt-get -y install pritunl-client
...
ln: failed to create symbolic link '/etc/resolv.conf': Device or resource busy
dpkg: error processing package resolvconf (--configure):
 installed resolvconf package post-installation script subprocess returned error exit status 1
...
dpkg: dependency problems prevent configuration of pritunl-client:
 pritunl-client depends on resolvconf; however:
  Package resolvconf is not configured yet.

dpkg: error processing package pritunl-client (--configure):
 dependency problems - leaving unconfigured

```

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [October 4, 2022, 7:06am UTC](https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431/4 "2022-10-04T07:06:55Z")

</div>

The Pritunl Client requires a systemd service, that will need to be started with `pritunl-client-service`

---

<div class="post-metadata">

**Author:** ![s2504s](https://forum.pritunl.com/user_avatar/forum.pritunl.com/s2504s/32/504_2.png) [@s2504s](https://forum.pritunl.com/u/s2504s)\
**Post date:** [August 2, 2023, 12:08pm UTC](https://forum.pritunl.com/t/docker-and-or-kubernetes-official-support/431/5 "2023-08-02T12:08:06Z")

</div>

If we use containerized Pritunl client we run `pritunl-client-service` into background mode, b/c container does not have systemd at all

```auto
pritunl-client-service &
pritunl-client add pritunl://xxxxx

```

and it works. Of course, we added watchers for the background process and blah-blah-blah, but this is not a Pritunl story 🙂
