I started out using Rancher when getting into Docker containers, kubernetes, etc. I really like it. A lot of people seem to be fans of Portainer so i just set up a VM to test that out as well. I had thought about setting up Portainer on my existing "production" (home lab) environment but it's so easy to spin up a few new VM's since you don't need a log of resources just to run a few docker containers.
What i don't like about Portainer is that compose files are stored in it's database. And if you run compose files outside of it, they will have 'limited control' status.
Horrible recommendation. Rancher version 1.6 has so many bugs and Rancher all in all has such BAD documentation, it's insane! A mere rancher server upgrade means you have to recreate all your load balancers and recreate some of the rancher-system containers manually. It is so lously, it's unbelievable how it has surived in the market. The security standards are insane! If you have a single node Rancher, you're dependent on a separate firewall, otherwise you cannot manipulate iptables, because Rancher keeps recreating the NAT rules, which means the containers will always be directly exposed to the internet. You'd need to change the MANGLE chain in order to filter (this goes against any standard iptables rule - you don't do filterting in MANGLE tables). It creates so much crap into your system, that you're completely dependent on it and you cannot easily move away, unless you move the containers/volumes altogether. It's a whole mess. Rancher is by no means production-ready!
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
I started out using Rancher when getting into Docker containers, kubernetes, etc. I really like it. A lot of people seem to be fans of Portainer so i just set up a VM to test that out as well. I had thought about setting up Portainer on my existing "production" (home lab) environment but it's so easy to spin up a few new VM's since you don't need a log of resources just to run a few docker containers.
Thank you for sharing. I'm lways looking forward the comparation between Shipyard and Rancher.
Excellent short presentation. Thanks.
well said, love the end summary
What i don't like about Portainer is that compose files are stored in it's database. And if you run compose files outside of it, they will have 'limited control' status.
thank you great video!
You really sound like MKBHD !!
Horrible recommendation. Rancher version 1.6 has so many bugs and Rancher all in all has such BAD documentation, it's insane! A mere rancher server upgrade means you have to recreate all your load balancers and recreate some of the rancher-system containers manually. It is so lously, it's unbelievable how it has surived in the market. The security standards are insane! If you have a single node Rancher, you're dependent on a separate firewall, otherwise you cannot manipulate iptables, because Rancher keeps recreating the NAT rules, which means the containers will always be directly exposed to the internet. You'd need to change the MANGLE chain in order to filter (this goes against any standard iptables rule - you don't do filterting in MANGLE tables). It creates so much crap into your system, that you're completely dependent on it and you cannot easily move away, unless you move the containers/volumes altogether. It's a whole mess.
Rancher is by no means production-ready!