I was investigating what it would take to create a docker container and have the logs go to their appropriate log files in addition to being available via the docker logs command (don’t remember why). During the course of doing that I didn’t accomplish my goal but I did learn that the typical I/O streams of STDOUT and STDERR are the defaults. So it’s essentially just piping those output streams directly to the command.

While changing what source image a docker container in unRaid was using, the Docker managment service encountered an error. The error itself I forgot to write down. But what is normally a typical process of “download new image, stop old container. create new container, cleanup old image.” was interrupted and it left the container in a down state. This wasn’t good primarily because I am lazy and didn’t want to spend the mental power and try to come up with what the previous config options were so there can be no change except what image is being used.

I woke up this morning to my RSS feed misbehaving. FreshRSS was popping up an error along the lines that it was unable to make an internet connection. This was a little odd as I was connected over the local network to the app. It was loading at all which meant it could connect. I won’t bore you with how I found the problem, but the root partition of the server was full.

I keep my notes in markdown files in a git repo my primary editor is a tool called obsidian.md. I’ve got minor gripes and for the most part I’ve got it syncing well and working well. However, a nice to have feature would be to share individual documents with the public. Couple examples, keeping a digital recipe box for the household to read from or sharing TTRPG notes after a session.

I set up a splunk docker container recently and there were a couple what feel like oddities catching me up. Default debian doesn’t have world readable log files. This is not for production. But it’s okay for my homelab. Starting with this basic docker-compose file we made sure it worked. version: "3.6" services: so1: image: ${SPLUNK_IMAGE:-splunk/splunk:latest} container_name: so1 environment: - SPLUNK_START_ARGS=–accept-license - SPLUNK_PASSWORD ports: - 8000:8000 It’s simple, gets everything running without doing anything fancy.