Tutorial: Upgrade the Access Server Docker Image⁠

1. Connect to your server where your current Access Server Docker container is running. This is typically done via SSH:

   ssh your-username@your-server-ip

   1. 1

      Replace with your SSH user.

   2. 2

      Replace with the IP address of the server running Docker.

2. Once connected, run the following command to pull the latest Access Server version image from Ducker Hub:

   docker pull openvpn/openvpn-as:latest

   • This downloads the most up-to-date image, preparing it for deployment in later steps.

To preserve your existing configuration and data, ensure you identify which folder Access Server uses to store this information.

1. Run the following command to inspect the container:

   docker inspect openvpn-as

   • This command returns detailed information about the container.

2. Look for the "HostConfig": section, and within it, check the "Binds": array. An example output might look like:

   "HostConfig": {
       "Binds": [
           "/ExampleHostFolder/:/openvpn"
       ]
   }

3. The /ExampleHostFolder/ is the directory on the host system where Access Server stores configuration and database files. This path is critical for a successful upgrade.

1. Before running the upgrade container, stop and remove the existing Access Server container:

   docker stop openvpn-as
   docker rm openvpn-as

   • Stopping and removing the old container ensures no conflicts when running the new one.

Now that you've downloaded the latest image and identified the data folder used by the previous container, you can launch the new container.

• Ensure the path to the data folder remains the same to allow the new container to use your existing configuration:

  docker run -d \
    --name=openvpn-as --device /dev/net/tun \
    --cap-add=MKNOD --cap-add=NET_ADMIN \
    -p 943:943 -p 443:443 -p 1194:1194/udp \
    -v <path to data>:/openvpn \
    --restart=unless-stopped \
    openvpn/openvpn-as

  1. 1

     Provides access to the TUN device for VPN traffic.

  2. 2

     Allows the container to create device nodes.

  3. 3

     Grants the container the necessary network administration capabilities.

  4. 4

     Opens up the necessary ports: 943 for the Admin Web UI, 443 for TCP, and 1194 for UDP.

  5. 5

     Location for storing the Access Server configuration files. Replace <path to data> with your preferred file path.

  6. 6

     Tells Docker to automatically restart the container if it stops unexpectedly or the Docker daemon restarts, but not if you explicitly stop it.

• This command starts a new container running the latest Access Server version with the previous configuration and database files.

1. Verify a successful upgrade by checking the status of the container:

   docker ps

2. Additionally, you can access the Access Server Admin Web UI to confirm that the version is updated and your settings are intact.