Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Wow, that's very unfortunate. If you installed docker through package manager and have added yourself to the group I believe this to be self-imposed, I don't know which mechanism Docker uses to give access to users in the group to its service, but seems related to that since it looks like the service is running but just your user can't access it. To confirm it's just that run the compose command as root, i.e.
sudo docker compose up
, this is not ideal but if that works you know it's a permission problem with your user.You seem to know your way around Linux, so it's probably not something obvious. I'm almost sure it's something stupid and self imposed, I've done my fair share of stupid shit like leaving a config file malformatted or deleting a library or installing something through manually copying files only for something else to break because I overwrote something important.
OK, well that works enough to access the specified port and loads the webapp. So that's cool. :) There's a tcp error printed in the page itself but ?maybe? that is caused by improperly running it.
It could well be some self imposed error. But I'm always gonna be making those. If it is, it happened because I was trying to solve some other rudimentary issue. I've never gotten anything functional with this so it's not like I was trying to do something fancy and got in over my head.
Part of the issue with docker in this attempt and other times is it doesn't give good enough errors/output to diagnose. It's really kind of you to help me here but I can't call you every step. The documentation is too focused on making things look simple even when they're not, and therefor glossing over whatever system weirdies are getting in the way. You identified a user issue and even I suspected it (that's why I tried all those commands with and without
sudo
in the above comment). Yet it is not in the official documentation as a potential cause of said error. And now that I have confirmed it, I have no idea how to solve it. I see in my browser history I've previously looked up "rootless mode". Maybe that's how I screwed this up in the first place.Moral of the story is, docker becomes a mess immediately. :D