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
Where do I find that information? What is the exact command that I should type?
https://letmegooglethat.com/?q=docker+logs+command
Lol. Thank you. Part of the frustration of being a beginner in any space is that it's not easy to discern which questions have simple answers and which are more complicated.
From the search you linked, it looks like this is as simple as typing the command
docker logs
I'll give that a try, once I have access to the server again.
Also if you've never seen it, lazydocker might be something up your alley.
It's a TUI, but it provides easy access to docker containers, logs, updating/restarting/stopping/etc them and so on.
It looks like in this case the answer was a little deeper than a simple search, but no worries - you set me in the right direction. I'll add the solution to the post.