For anyone watching this video now, the workaround mentioned at 9:14 is no longer needed and the container can be installed and run directly like any other container. I'm on hAP ax3 ROS 7.15.2.
So i was having this problem previously and mikrotik helped me pretty sure you got the video on the same forum . Definitely this video will help a lot of people i wish there was a video before searching for a week . thank you and I love your videos .
Yeah I tried making this work for a long time before just giving up. Never considered or would have thought about deleting the hidden file via FTP to get this to work (makes me wonder if there are other containers not working that can be fixed the same way) If you were the person that posted on the forums then Thank You! It is because of you that they looked at this and posted the workaround :D!
Always great content! Would it be possible to cover container network in combination with VLAN's? Somehow I have been unable to connect my veth to my vlan setup.
NB!!!: Please confirm your device can support containers first by seeing that it has the container package, if it is available you will first need to install the container package before you can change the device mode to container. NB2!!!!: Please note that a bug will still cause permission errors when upgrading to 7.7 STABLE with the Kuma_data files, in essence you will have to delete the files in the Kuma_data directory to gain access to the container and start it again, this means a complete reconfiguration. This is definitely not intentional behavior so use at your own risk/frustration or wait to upgrade once MT fixes the bug :) Hope you guys are doing well, just want to post some reference material here that you can use with the video! (Please use the time stamps to skip to different parts of the video that may interest you) Uptime-Kuma docs: github.com/louislam/uptime-kuma MikroTik Containers: help.mikrotik.com/docs/display/ROS/Container
my TILE architecture router supports containers but mikrotik doesnt give the container package on their site. is there a work around? do you think i can set containers up without the container package? is the container package a must?
I'm having an issue where uptime kuma is pushing 10 pings per 10 seconds on mikrotikes and causing dos attack flags and uptime kuma shows it as packet loss. Wondering if you have solution. I have considered bumping up the icp amount. Haven't really messed with the allow rules. But is there a setting in uptime kuma to drop the pings to like 3 instead of 10?
What are you using to SFTP? Just a terminal client? Can run an "ls -la" to see hidden files. Else you could try connecting with WinSCP. Just make sure that you set Show Hidden Files in the Panels section of the Preferences menu. You also need to try and start the container at least once so that it generates the file.
@@TheNetworkBerg Thanks, I will take a look further, I have done the above prior to my message and could not see anything, removed the container, removed all directories, started again and the ran the container to generate the directory and still dont see that file. I see it on a CHR , but not generating on the RB3011 I am trying to test it on. Will keep you posted if I come right
I might be able to make a video on it, although it should be a few simple steps 1. Install Wine 2. Download Winbox from MikroTik 3. use wine to run Winbox Commands for me looks like this sudo apt install wine cd Downloads wine winbox64.exe This brings up Winbox normally like on Windows with all features working like mac-telnet or Romon
I've upgraded to 7.7 stable and I indeed had issues where I had to remove all the kuma_data files before I could start the container again, however, it works fine afterwards even when rebooting. Just the upgrade breaks this container and is definitely a bug that MT needs to sort out. I have pinned my suggestions in the top comment. Thanks for letting me know what your experience was.
@@TheNetworkBerg Very strange, but in my situation reboot also affected. What about upgrade - of course it will work if you delete and recreate data - but you lost data.... Because I tried to backup data files, then restore it via sftp - doesn't help. I will not argue - probably it was bug on my side with reboot. But with upgrade, if you lost the date, it doesn't make sense. I hope, it future mikrotik will solve the issues with permissions for containers. But for now - just for fun.
For anyone watching this video now, the workaround mentioned at 9:14 is no longer needed and the container can be installed and run directly like any other container.
I'm on hAP ax3 ROS 7.15.2.
Nice, thanks for the info, we have the identical model and version, cant wait to try this!
I was wondering, how were you able to run the container? I didnt have enough space
@@joker28666 I'm running it off a USB drive along with Adguard Home.
Uptime kuma is great, I bridge my network devices using Mikrotik + ZeroTier then monitor it using uptime kuma and using API discord for notification.
Excellent, another great tutorial including the MikroTik workaround! Thank you :)
Thank you! Finally something small and powerful for monitoring. :)
Great video, very informative, looking to get into containers on mikrotik myself. Thank you for posting the music as well, Outland 85 is sick
So i was having this problem previously and mikrotik helped me pretty sure you got the video on the same forum . Definitely this video will help a lot of people i wish there was a video before searching for a week . thank you and I love your videos .
Yeah I tried making this work for a long time before just giving up. Never considered or would have thought about deleting the hidden file via FTP to get this to work (makes me wonder if there are other containers not working that can be fixed the same way)
If you were the person that posted on the forums then Thank You! It is because of you that they looked at this and posted the workaround :D!
@@TheNetworkBerg yeah I'm sure that there will be more containers that requires special configuration
I love your channel and way of presenting.
I appreciate that!
Wonderful Brother. a new way to optimize things
Very nice video and project, TNX.
The best as always! thank you The Network Berg! :)
Kudos to you and Anton's
Always great content! Would it be possible to cover container network in combination with VLAN's? Somehow I have been unable to connect my veth to my vlan setup.
Great, thank you i appreciate
NB!!!: Please confirm your device can support containers first by seeing that it has the container package, if it is available you will first need to install the container package before you can change the device mode to container.
NB2!!!!: Please note that a bug will still cause permission errors when upgrading to 7.7 STABLE with the Kuma_data files, in essence you will have to delete the files in the Kuma_data directory to gain access to the container and start it again, this means a complete reconfiguration. This is definitely not intentional behavior so use at your own risk/frustration or wait to upgrade once MT fixes the bug :)
Hope you guys are doing well, just want to post some reference material here that you can use with the video! (Please use the time stamps to skip to different parts of the video that may interest you)
Uptime-Kuma docs:
github.com/louislam/uptime-kuma
MikroTik Containers:
help.mikrotik.com/docs/display/ROS/Container
THANKS a LOT ;)
Thanks a lot
thanks great video ..if you’re taking requests: how about bind9 in a container on mikrotik next? 🙂
Great suggestion, will keep it on my radar as well ^^
so cool ui
IS there a way to monitor state change on a host (for loadshedding determination)?
my TILE architecture router supports containers but mikrotik doesnt give the container package on their site. is there a work around? do you think i can set containers up without the container package? is the container package a must?
hAP ax³ v7.8 running with no problems, .type fixed
I saw the update, looking forward to test it out when my own hAP ax3 arrives next week :D!
I'm having an issue where uptime kuma is pushing 10 pings per 10 seconds on mikrotikes and causing dos attack flags and uptime kuma shows it as packet loss. Wondering if you have solution. I have considered bumping up the icp amount. Haven't really messed with the allow rules. But is there a setting in uptime kuma to drop the pings to like 3 instead of 10?
What is memory consumption of this docker?
How to install Prometheus + Gafana SNMP on Docker Mikrotik
Thanks for this, I am trying this on a RB3011UiAS and when I go into the router via sftp into the same directory I dont have that file strangly.
What are you using to SFTP? Just a terminal client? Can run an "ls -la" to see hidden files. Else you could try connecting with WinSCP. Just make sure that you set Show Hidden Files in the Panels section of the Preferences menu. You also need to try and start the container at least once so that it generates the file.
@@TheNetworkBerg Thanks, I will take a look further, I have done the above prior to my message and could not see anything, removed the container, removed all directories, started again and the ran the container to generate the directory and still dont see that file. I see it on a CHR , but not generating on the RB3011 I am trying to test it on. Will keep you posted if I come right
a tutorial for outline vpn server on mikrotik docker container please
i am getting the following error
error response getting manifests: 404
What mikrotik model you use un this video tutorial?
It's an x86 (A virtual machine that runs on my hypervisor)
@@TheNetworkBerg thanks!
What was your first video of containers?
Can you give me instructions on how to install Winbox on Ubuntu? I followed it online but it didn't work.
I might be able to make a video on it, although it should be a few simple steps
1. Install Wine
2. Download Winbox from MikroTik
3. use wine to run Winbox
Commands for me looks like this
sudo apt install wine
cd Downloads
wine winbox64.exe
This brings up Winbox normally like on Windows with all features working like mac-telnet or Romon
Doesn't continue to work if you restart router or upgrade to 7.7
That's unfortunate, It was working with the 7.7rc4 build I was using. Will upgrade to 7.7 stable and see if I have similar issues.
I've upgraded to 7.7 stable and I indeed had issues where I had to remove all the kuma_data files before I could start the container again, however, it works fine afterwards even when rebooting.
Just the upgrade breaks this container and is definitely a bug that MT needs to sort out. I have pinned my suggestions in the top comment.
Thanks for letting me know what your experience was.
@@TheNetworkBerg Very strange, but in my situation reboot also affected. What about upgrade - of course it will work if you delete and recreate data - but you lost data.... Because I tried to backup data files, then restore it via sftp - doesn't help. I will not argue - probably it was bug on my side with reboot. But with upgrade, if you lost the date, it doesn't make sense. I hope, it future mikrotik will solve the issues with permissions for containers. But for now - just for fun.
so its basicaly an open source uptimerobot, almost 1to1 feature set and colour pallet.