As of 0.13.0, upgrading Netmaker is a manual process. This is expected to be automated in the future, but for now, is still a relatively straightforward process.
Critical Notes for 0.13.X¶
If upgrading from 0.12 to 0.13, refer to this gist: https://gist.github.com/afeiszli/f53f34eb4c5654d4e16da2919540d0eb
Critical Notes for 0.10.0¶
At the time of this writing, an upgrade process has not been defined for 0.10.0. DO NOT follow this documentation to upgrade from a prior version to 0.10.0. An upgrade process will be defined shortly. For now, if you seek to upgrade to 0.10.0, you must clear your server entirely (docker-compose down –volumes), uninstall your netclients, and re-install netmaker + netclients.
Upgrade the Server (prior to 0.10.0)¶
To upgrade the server, you only need to change the docker image versions:
Change gravitl/netmaker:<version> and gravitl/netmaker-ui:<version> to the new version.
Save and close the file
docker-compose up -d
Upgrade the server after v0.16.1¶
There have been changes to the MQ after v0.16.1. You will need to make changes to the docker-compose.yml and get the new mosquitto.conf files. We recommend upgrading your server first before any clients.
Start by shutting down your server with
You then need to get the updated mosquitto.conf file. You will also need to get the wait.sh file and make sure it is executable.
wget -O /root/mosquitto.conf https://raw.githubusercontent.com/gravitl/netmaker/master/docker/mosquitto.conf wget -q -O /root/wait.sh https://raw.githubusercontent.com/gravitl/netmaker/develop/docker/wait.sh chmod +x wait.sh
Then make the following changes to the docker-compose.yml file.
change image tags in netmaker and netmaker-ui service sections to
- In your netmaker service section:
In the volumes section, change
In the environment section, add
- In the mq service section:
Add an environment section and add
In the volumes, add
You need to make some changes to the labels. a few of them just need
mqtt. The labels should look like this:
- traefik.enable=true - traefik.tcp.routers.mqtt.rule=HostSNI(`broker.NETMAKER_BASE_DOMAIN`) - traefik.tcp.routers.mqtt.tls.certresolver=http - traefik.tcp.services.mqtt.loadbalancer.server.port=8883 - traefik.tcp.routers.mqtt.entrypoints=websecure
Your MQ section should look like this after the changes.
mq: container_name: mq image: eclipse-mosquitto:2.0.11-openssl depends_on: - netmaker restart: unless-stopped command: ["/mosquitto/config/wait.sh"] environment: NETMAKER_SERVER_HOST: "https://api.NETMAKER_BASE_DOMAIN" volumes: - /root/mosquitto.conf:/mosquitto/config/mosquitto.conf - /root/wait.sh:/mosquitto/config/wait.sh - mosquitto_data:/mosquitto/data - mosquitto_logs:/mosquitto/log expose: - "8883" labels: - traefik.enable=true - traefik.tcp.routers.mqtt.rule=HostSNI(`broker.NETMAKER_BASE_DOMAIN`) - traefik.tcp.routers.mqtt.tls.certresolver=http - traefik.tcp.services.mqtt.loadbalancer.server.port=8883 - traefik.tcp.routers.mqtt.entrypoints=websecure
You should be all set to
docker-compose up -d
Note: Your clients will show in warning until they are also upgraded. The upgrade for clients is the regular upgrade, then do a
docker logs mq should be showing logs like this:
Waiting for netmaker server to startup Waiting for netmaker server to startup Waiting for netmaker server to startup Waiting for netmaker server to startup Waiting for netmaker server to startup Waiting for netmaker server to startup Waiting for netmaker server to startup Starting MQ... 1665067766: mosquitto version 2.0.11 starting 1665067766: Config loaded from /mosquitto/config/mosquitto.conf. 1665067766: Loading plugin: /usr/lib/mosquitto_dynamic_security.so 1665067766: Opening ipv4 listen socket on port 8883. 1665067766: Opening ipv6 listen socket on port 8883. 1665067766: Opening ipv4 listen socket on port 1883. 1665067766: Opening ipv6 listen socket on port 1883. 1665067766: mosquitto version 2.0.11 running 1665067769: New connection from 172.21.0.2:34004 on port 1883. 1665067769: New client connected from 172.21.0.2:34004 as L0vUDgN0IZFru9VaS6HoRL5 (p2, c1, k60, u'Netmaker-Admin'). 1665067769: New connection from 172.21.0.2:34006 on port 1883. 1665067769: New client connected from 172.21.0.2:34006 as ydmOjmIcw9nNaT1GB1q97Se (p2, c1, k60, u'Netmaker-Server').
If you see mq logs about waiting for netmaker server to startup after longer period than usual, check if your traefik certs are generated correctly. You can try to resolve with
docker restart traefik
Upgrade the server to use 0.17.0 after Upgrading for 0.16.3¶
Version 0.17.0 uses Caddy instead of traefik.
Open a Terminal window (shell prompt). To set up Caddy you’ll need to configure the Caddyfile as follows.
If you are using the Community Edition of Netmaker use this command:
wget -O /root/Caddyfile "https://raw.githubusercontent.com/gravitl/netmaker/master/docker/Caddyfile"
If you are using the Enterprise Edition of Netmaker use this command:
wget -O /root/Caddyfile "https://raw.githubusercontent.com/gravitl/netmaker/master/docker/Caddyfile-EE"
Once you have a Caddyfile you’ll need to run these two commands:
sed -i "s/NETMAKER_BASE_DOMAIN/$NETMAKER_BASE_DOMAIN/g" /root/Caddyfile sed -i "s/YOUR_EMAIL/$EMAIL/g" /root/Caddyfile
Where $NETMAKER_BASE_DOMAIN is the base domain you used for your Netmaker setup (the part after “dashboard.” in your Dockerfile) and $YOUR_EMAIL is your email address.
If users still want to keep using Traefik as the reverse-proxy instead of Caddy for v0.17.0 and above, refer to this docker-compose file https://gist.github.com/alphadose/1602e5dcba500f75ab0b873d4441236b
Edit the above docker-compose file
sed -i 's/NETMAKER_BASE_DOMAIN/<your base domain>/g' docker-compose.yml sed -i 's/SERVER_PUBLIC_IP/<your server ip>/g' docker-compose.yml sed -i 's/REPLACE_MASTER_KEY/<your generated key>/g' docker-compose.yml sed -i "s/REPLACE_MQ_ADMIN_PASSWORD/<your generated password>/g" docker-compose.yml
After that finally start the netmaker server
sudo docker-compose up -d
Upgrade the Clients (prior to 0.10.0)¶
To upgrade the client, you must get the new client binary and place it in /etc/netclient. Depending on the new vs. old version, there may be minor incompatibilities (discussed below).
Find the appropriate binary for your machine.
Download. E.x.: wget https://github.com/gravitl/netmaker/releases/download/vX.X.X/netclient-myversion
Rename binary to netclient and move to folder. E.x.: mv netclient-myversion /etc/netclient/netclient
netclient –version (confirm it’s the correct version)
This last step helps ensure any newly added fields are now present. You may run into a “panic” based on missing fields and your version mismatch. In such cases, you can either:
Add the missing field to /etc/netclient/config/netconfig-yournetwork and then run “netclient checkin”
Leave and rejoin the network
Upgrading server and client to 0.18.5¶
NB: Upgrading to this version requires your server to be currently running v0.17.1
Steps to upgrade
SSH to your Netmaker server
Run the upgrade script:
wget https://raw.githubusercontent.com/gravitl/netmaker/release_v0.18.5/scripts/nm-upgrade.sh && chmod +x nm-upgrade.sh && ./nm-upgrade.sh(for v0.18.x, check releases page)
Follow prompts until the upgrade process on the server is completed.
Upgrade all netclients.
Manually go to each client machine and download new netclient binary from here
./netclient install(Windows users must run with Admin Powershell first. Also use
.\netclient.exe installto install)
NB: Windows and Mac users, do not Open GUI until above steps are completed.
Dynamic Portwas on, you may need to manually adjust port to
51821after upgrading the client