Docker

DBeaver, which lets me edit PostgreSQL data in bulk through a GUI while writing almost no SQL, had been invaluable. It is Java based, though, so it is fairly heavy to start up, and I had come to want something a bit lighter for looking at several databases together. That was when I found DBX. It is free, supports many databases, and is said to run lightly. I decided to try building it into my Traefik-fronted Docker environment. [Read More]

I noticed that the Web UI of the Pi-hole I run at home (http://127.0.0.1:8053/admin) had become completely unreachable. All I got back was Connection reset by peer, and neither the browser nor curl could see anything. DNS resolution (port 53) was still working fine, so there was no real damage. As far as docker ps went the container was shown as healthy, so I had not been worried, but when I looked into it I found that the problem itself went back six days, to 2026-08-01. [Read More]

The IP address ledger I had been keeping in GoogleSpreadSheet was no longer keeping up as the number of devices grew. The IP addresses actually in use and what the sheet said drifted apart more and more, and I was reaching the limit of taking stock by hand, so I decided to start phpIPAM with Docker and move IP management there. Starting it with Docker I settled on the following docker-compose.yml. [Read More]

I publish various services from my home server with Docker, so when OrbStack (Docker) does not work properly it seriously disrupts my daily work and my use of those services. This time, when I tried to start OrbStack on macOS, not only did the Docker containers fail to come up, the app itself did not launch at all and quit immediately, which made me quite nervous. Here I record how I investigated the cause and recovered. [Read More]

Introduction: the late-night “what was this port again?” problem When you run servers, you repeatedly end up in the situation where you see an alert in the middle of the night, SSH into the machine, and think “what is listening on this port again?” Until now I combined netstat / ss / lsof / nmap / systemctl / docker ps and worked out the identity and the origin of the process by hand. Recently I started using a CLI tool called witr (Why is this running), and because it explains in a single command even why a process exists, my investigation flow has changed considerably. [Read More]

The root partition (/) of the machine I run Docker on was getting tight, so I moved /var/lib/docker These days, when you install Linux without thinking about it, the automatic configuration often gives the root partition (/) something small such as 30GB. When you run Docker, /var/lib/docker grows and grows, so / ended up in a state close to full. So I moved it to /home, which is on a separate partition and has room to spare [Read More]

I wanted to manage software licences as well as the appliances and assets in my home, so I looked around for a good open source option, found the IT asset management system Snipe-IT, and set it up right away. This is how to install it with Docker Installation and configuration Copy $ git clone https://github.com/snipe/snipe-it.git Edit .env.docker Copy APP_DEBUG=false # please regenerate the APP_KEY value by calling `docker-compose run --rm snipeit bash` and then `php artisan key:generate --show` and then copy paste the value here APP_KEY=base64:3ilviXqB9u6DX1NRcyWGJ+sjySF+H18CPDGb3+IVwMQ= APP_URL=http://localhost:8000 -APP_TIMEZONE='UTC' -APP_LOCALE=en +APP_TIMEZONE='Asia/Tokyo' +APP_LOCALE=ja Port 8000 is used by default, so if you want to change it, change ports in docker-compose.yml [Read More]

This is a follow-up to Building a mail server with Sakura VPS + Docker + Freenom , in which I tighten up the security a little If the server from last time is running under docker, stop it Copy $ docker-compose down Closing imap and submission In the previous article I confirmed that imaps and smtps communication works, so I close imap and submission docker-compose.yml (only the changed parts are shown) [Read More]

TL;DR I tried building a mail server with Docker on a Sakura VPS I will skip registering a domain on Freenom and how to use Cloudflare Linux(Debian10) Docker is assumed to be already installed A domain name has been obtained from Freenom and registered in a DNS such as Cloudflare Freenom : example.com (fictitious name) Sakura VPS: 11.22.33.44 (fictitious IP) For this server build I referred to the sites below [Read More]

On my home server I run several nginx-proxy Docker containers, and I also make them accessible from outside on my own domain. Of course, on the fiber router facing the WAN I have ports 80 and 443 open, and connectivity from outside is confirmed. In this kind of setup, a symptom where access from outside was not possible started happening at irregular intervals Symptoms When the problem shows up from outside, access becomes impossible with a 403 Fobidden like the one below [Read More]