Wow, super awesome! That means that Yunohost can have Lemmy as package, and maybe as Lemmy grows via others like Installatron (via regular hosting providers) and similar as well. And thanks @kinetix@lemmy.ca
Thats great, I didnt even know that Yunohost was blocked by our lack of documentation.
Thanks! It is very uncommon for Yunohost apps to use Docker. I’ve looked up some history about this :
I made this package because it was requested by someone. And honestly I did not wanted to use Docker for this. But I did not had time to figure out on how to install it without Docker…
Then why this package uses Docker? It’s because the developers of the core app do not support simple installation. And packaging without documentaion is time consuming.
So now that this has been fixed, the next step could be to somehow make the manual install option aware within the Yunohost community (I am not sure what is the best way for this, hopefully others can) and then hopefully a Lemmy package for Yunohost can grow from level 0 to level 6 or 7 or 8, and by doing so have much more “exposure” among Yunohost users.
So now that this has been fixed, the next step could be to somehow make the manual install option aware within the Yunohost community
I simply made a comment in the thread you linked haha
Nice, thanks ! :)
Considering how many apps use docker nowadays, that really surprises me that they wouldn’t support it. There’s that linuxserver docker repository that’s packaged hundreds of applications for docker.
Yunohost is focused on easy install on among others a VPS. If the VPS provider runs OpenVZ or LXC in their infrastructure then Docker is either not possible, or with limitations or first needs tweaking by the provider.
Imho I think yunohost is fine for what it is. adding Docker support to this would just make it unnecessarily complex.
However an YunoHost alternative that was build from ground up to be docker based would be cool.
docker is really bad for security and adds a lot of unnecessary complexity
Docker is not bad for security, unless you do insecure things like exposing your Docker socket or running random workloads as root, however those are just as insecure under systemd.
It has some weird behaviour, for example ufw rules dont apply to Docker.
This is not insecure. It is surprising if you don’t know how containers work, but in a real deployment you’d only bind to localhost and use a reverse proxy and that is perfectly safe.
Docker runs the whole daemon as root and has a large attack surface. Also, it has a lot of footguns that can mislead the user. Its security track record speaks for itself: https://www.cvedetails.com/product/28125/Docker-Docker.html?vendor_id=13534
How is this different from say, SystemD? It runs as root and has a larger attack surface.
The link you pointed out has every CVE for every application packaged as Docker image. Would you make the same point that APT or AppImage is insecure because there are insecure applications packaged that way?
Hey, that’s cool that someone formatted them for the lemmy docs… I think I’ll have to get in there and try and push some updates. Heh, I also see mention of things like “respective authors” with no authors mentioned. I’ll try and get some changes merged soon.
Oh. THAT IS GREAT.
I found some more written down reasons for Yunohost not wanting to use Docker :
Disclaimer
This package installs Discourse without Docker, for several reasons (mostly to support ARM architecture and low-profile servers, to mutualize nginx/postgresql/redis services and to simplify e-mail setup). As stated by the Discourse team:
The only officially supported installs of Discourse are Docker based. You must have SSH access to a 64-bit Linux server with Docker support. We regret that we cannot support any other methods of installation including cpanel, plesk, webmin, etc.
So please have this in mind when considering asking for Discourse support.
