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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
Why run Docker Desktop when it's installable as a cli service?
What are you actually trying to achieve?
ease of use.
I'm a noob at networking.
there's only one way to get better at it. by doing it.
Or if it’s not something that’s valuable to you just do it the easy way.
Docker Desktop isn’t needed on Linux. If you want a UI, try Portainer
Don't think Docker Desktop would simplify networking, unless it added a new feature since I last used it ~2 years ago.
Just throw your services in a docker-compose.yml file, create a docker bridge network, and assign the:
To the services in the yaml file, specify the ports it want’s to open with
And let it start up. If you want to get more complicated suggest reading the man page which really isn’t that long of a read.
Networking really cannot be simplified, you have to view it in a logistical way of how is Point A communicating with Point B which where Docker bridge networks come into play, they make the communication easy, if all your containers are all on the same docker network all you have to do is specify http://ContainerName:Port for them to communicate back and forth internally.
Check out CasaOS. Really easy to set up.
What does networking have to do with docker? You haven't explained what you're trying to achieve.
Access containers remotely
As a Mac user who's migrated over to Linux over the past year or so, I've got an idea of where OP is coming from.
Docker on macOS is accessed via a Desktop GUI, so you can easily see what you have installed, how it's running, etc... So when I shifted over to Linux, I was thrown off by there being no such tool. I wasn't used to using a terminal to do everything, and grumbled quite a lot about there being no Docker Desktop GUI, given how many self-hostable services run through Docker.
I've since gotten used to it, but it really is quite jarring.
There are a lot of Docker GUI tools out there. There just isn't Docker Desktop. Here are a few:
Oh aye, I get it. But when you're new to the platform and trying to work with tools that are familiar, you don't know about any of that.