Dockhand: The Easiest Way I’ve Found to Manage and Update Docker Containers [YouTube Release]

Additional Resources:

Dockhand site https://dockhand.pro/

Self-Hosted SSL Simplified: Nginx Proxy Manager

My video on OSI Models

Connect With Us

Lawrence Systems Shirts and Swag

►👕 Lawrence Systems

AFFILIATES & REFERRAL LINKS

Amazon Affiliate Store
:shopping_cart: Lawrence Systems's Amazon Page

UniFi Affiliate Link
:shopping_cart: Ubiquiti Store

All Of Our Affiliates help us out and can get you discounts!
:shopping_cart: Partners We Love – Lawrence Systems

Gear we use on Kit
:shopping_cart: Kit

Use OfferCode LTSERVICES to get 10% off your order at
:shopping_cart: Tech Supply Direct - Premium Refurbished Servers & Workstations at Unbeatable Prices

Digital Ocean Offer Code
:shopping_cart: DigitalOcean: AI-Powered Unified Inference Cloud Infrastructure

HostiFi UniFi Cloud Hosting Service
:shopping_cart: HostiFi - Fast and Reliable UniFi in the Cloud

Protect your privacy with a VPN from Private Internet Access
:shopping_cart: https://www.privateinternetaccess.com/pages/buy-vpn/LRNSYS

Patreon
:money_bag: https://www.patreon.com/lawrencesystems

Chapters
00:00 What is Dockhand
01:11 Source Code and License
01:50 Roadmap
02:12 Free VS SMB VS Enterprise
02:50 Dockhand Security and Telemetry
04:08 How To setup Dockhand with Docker Compose
04:49 User Authentication Setup
05:31 Configuring Local & Remote Environments
08:52 Managing Containers & Updates
10:15 Container Logs
10:52 Shell Access
11:11 Stacks
11:27 Managing Images and Volumes
12:00 Activity logging and schedules
12:23 Container Vulnerability Scanning

This video gave me the confidence to switch. Question for you all. I switch over to DockHand and I was wondering how do you all track what version you a running of service when there is an update available… so you know what to rollback to if there is an issue. it seems like there isn’t anything native. What the best practice. Sometimes problems aren’t discovered until long after update.

If you are using compose files with the tag latest you can edit that to be the previous version. But that may not work in every case because some updates may also update the data to fit the new version meaning you would have to roll back the data as well. A simple, but not really elegant approach is to run docker in a VM and roll that VM back which of course comes with the problem that it roll everything back.

In practice most of the applications I use are very stable so it’s a non-issue except for one app: https://twenty.com/ . I have not talked much about this app because it feels very beta and has had a lot of breakage from updates and is really the only one update with an immediate plan to roll back after testing.

Does this work with images compiled using docker build?

Wasn’t sure where to ask this… it’s about the CVE for trivy with respect to Dockhand using it to scan images. https://www.docker.com/blog/trivy-supply-chain-compromise-what-docker-hub-users-should-know/

Does this affect us. It seems some say since dockhand is only scanning the image and doesn’t pass it the .env or compose to scan, we are unaffected. That seem to make sense to me if that is true but I’m a newbie and don’t know if that is true.

hoping someone smarter and with more experience than me can confirm my understanding that we are not affected.

Yes, Dockhand’s security workflow is focused on the container image itself rather than the deployment configuration files so should be good.

1 Like

I might be crazy… never a good way to start… right?

Q1: Versioning of stack (compose and .env files)
I’ve been using dockhand and have been experimenting and changing my compose files alot as I fix things or add vars etc or limits etc. It’s gotten messy so I thought can’t I use Gitea to manage all these changes? and it can… but I have to shell out to set a message and commit and sync… as I couldn find a way to do it inside Dockhand. Does anyone know of a way to do this? I saw git-sync that watches for mods and pushes commits to gitea but doesn’t have a way to set the message… close to what I want.

In researching I ran across Komodo… It looked interesting but don’t know how it compares to Dockhand. I’m still new to this so I don’t thikn I should keep hopping from app to app… or I’ll never get a deep understanding of these apps.

Q2: Long term reporting
I had some Oom and flipfloping of unhealthing/healthy containers. But I don’t have a tool that keeps historical data. The graphs in Dockhand are real-time. Netdata was suggested. What do you all recommend? Ideally something that compliments Dockhand.

I don’t use a versioning system for mine, also I edit all of them via the command line on the Linux VM I have running Docker, not using Dockhand.

Netdata is great tool to have for troubleshooting but it’s not really for logging. Graylog is still my go to for ingesting all my logs.

1 Like