First of all, I said "compatible", not "exclusive". Second of all, why would it fail? Even if there was no tutorial how to run it directly on a system, a docker image carries all the information you need to run it on a given system. That's why we have Dockerfiles.

[–] dustyData@lemmy.world 5 points 9 months ago* (last edited 9 months ago) (2 children)

We like to think that what we are doing is the only valid way of doing things, specially when we are on the bleeding edge, and we forget that there's a whole world of people and possibilities (and a history before ourselves) for whom our one solution is not the holy grail for. Not every production environment or homelab is centered around containerization. Yes, it is cool and useful, but it doesn't exhaust every use case. Some people just don't use containers and if your app is exclusively available that way, then it's extra work to use it, or it just won't even be considered at all.

[–] dumpsterlid@lemmy.world 5 points 9 months ago

The wisdom of moving slowly and fixing things

[–] cevn@lemmy.world 3 points 9 months ago

Thank you. I would prefer not to install docker, that is just a personal preference, but so many apps are like uhh, we don’t know how to run this without Docker. Usually there is a way buried in layers of github issues but just like.. why.