Rather then have to run a separate device, it would be nice if I could have Vaultwarden running on the router.
1 Like
Docker isn't supported. Nor is rust. Bare metal installs would probably eat most of the device's available RAM:
Get a NAS that supports Docker, a RPi or build a hypervisor machine.
I guess unless Gl-inet were to release a device that had it in mind then the only other option would be a enthusiast SBC like RPi or BPI which is what I had been looking at, but being an enthusiast board it means needing to learn how to do everything yourself manually in OpenWRT which i wasn't quite ready for yet. I see Gl-iNet products being a stepping stone for me as it's still a consumer product and not as open but still a hell of a lot better then the mass-marketed brands/products.
For the MT6000 it might be possible, but docker already takes close to 1gb space, your next issue is if the container supports the architecture.
Though Docker on a OpenWrt router is not a very smooth experience, especially when you have to deal with the DSA implementation and docker network bridges this will work very cumbersome 
In the time I was using luci-app-dockerman the tab also had a chance of disappearing.
And routers have limited amounts of writes and then the flash breaks, so if you run something very query intensive (not sure how much that is on a password vault like vaultwarden), it can be risky.
You might need to install OpenWrt without the gl ui, because the chances are the dependencies don't even exist.
Since I moved to a NUC (GmkTek M5 plus) I run a cloud with jellyfin and jellyseerr, i run proxmox, use jenkins to build openwrt images, use it for lancaching and use portainer and have 2 m.2 nvmes with 4tb.
And it has a igpu, so it can transcode aswell.
Alot of things which are not on a router, or you always find something missing, and everything is supported. 
You're right that GL.iNet is far more open than most but there are certainly 'gotchas' given their customization of OWRT & use of a internally developed API, etc. Take a look thru some of my post history; you'll find me referencing & criticizing them quite openly, sometimes with work-arounds/alternative solutions.
That said I purchased a travel router to, unsurprisingly, travel with it. I accept there's limitations with using it as an appliance but I certainly like there's quite a few ways to extend it from a 'mere' travel router. It would be a different story if I was using a 'home' unit like the Flint v1, v2 or v3. On those I would flash straight OWRT & give up the GL GUI for more flexibility.
You strike me as someone with distinct interest in starting self-hosting/'home labbing.' Good for you. I'll just say it: pure (aka 'vanilla') OWRT does support Docker. You don't need to drop any money to 'cut your teeth' on it before picking up another SBC:
You can configure opkg to install to alternate locations, like an attached SSD.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.