ZimaOS 1.7 Update: Fixing the Broken
Update 24/08/2026: Zima OS fixed this in update v1.7.1… http://youtube.com/post/UgkxkNLoKxtVzMT6vbrR091ePKtC-QBdytVQ?si=MBzBedGmV9dqixT8
If you used the work around in this post and are now trying to set up gluetun and a torrent downloader, don’t forget you will need to stop and remove the existing containers via the dev console shown below.
sudo docker stop containerid and then sudo docker rm containerid.
Hey everyone. If you’re running a home server setup and thinking about updating your ZimaBoard, you might want to hold off for a second. The new ZimaOS update 1.7 breaks network_mode in compose files with the new app manager.
If you route traffic through a VPN container, this bug is a massive headache. This specific issue stops services such as Gluetun who rely on network_mode: service:gluetun from working.
The Quick Fixes
The simplest approach right now? Use the OG docker compose method via terminal, Either do not upgrade to ZimaOS 1.7 or downgrade via backups.
The Terminal Workaround
If you already updated and don’t want to restore a backup, alternatively there is a terminal workaround by setting up the compose file as our forefathers once did! We are going to use the OG method.
Here is exactly how you bypass the broken UI:
1.Backup and Remove the Existing App: Prevents port and naming conflicts.
Right-click the app on your ZimaOS desktop and select Manage. Navigate to the YAML tab and save this configuration somewhere safe. Once backed up, delete the app from your dashboard.
2.Access the Developer Console:
Navigate to Settings > General > Dev Console, and click View.
3.Connect via SSH:
Enable the SSH toggle, then click the Web-based terminal button to log in to your server.
4.Create the Compose File:
In the terminal, create a new Docker Compose file by running:
5. Update the broken code in your saved compose file first!
Change this….
To this….
6.Paste and Save:
Paste the YAML configuration you saved in Step 1 into the editor. Press Ctrl+O (then Enter) to save the file, followed by Ctrl+X to exit the Nano editor.
7.Spin Up the Container:
Finally, deploy your container in the background by running:
This bypasses the new ZimaOS 1.7 app manager and launches with native Docker controls. Your Gluetun network routing will instantly snap back to normal.
Keep an eye out for future ZimaOS patches, but until then, the terminal is your best friend.
Support the Channel ☕
If you found this guide helpful and are feeling extra appreciative, consider supporting the channel:
- Donate me a KO-FI: https://www.ko-fi.com/kltechvideos
- Follow on X (Twitter): https://x.com/kltechvideos (Help me beat the algorithm! 😂)
- Subscribe on YT (YouTube): https://www.youtube.com/@kltechvideos
- Checkout the Blog for more cool projects!: https://blog.kltechvideos.co.uk
- Don’t forget to let me know what content you are watching or reading on my socials!