<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Docker on Keldo.uk</title>
    <link>https://keldo.uk/tags/docker/</link>
    <description>Recent content in Docker on Keldo.uk</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 10 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://keldo.uk/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rathole</title>
      <link>https://keldo.uk/cloud/rathole/</link>
      <pubDate>Wed, 10 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/cloud/rathole/</guid>
      <description>&lt;p&gt;Ever since i moved behind starlinks cgnat i have been looking for a way to proxy my sites out to a public ip I have been using cloudflare tunnels for http/https however for tcp/udp i have been less successful as a patch job i setup playit.gg for git and minecraft however this has a very low amount of ports and does not let you chose which port to use.
My first major break through came when i started investigating oracle cloud free tier. My first attempt was using a software called pangolin and i just could not figure out its tunnelling. I then looked to wireguard and while i could create a tunnel i ran into a issue with ip config where the tunnel wouldn&amp;rsquo;t bind to the public ip only to the tunnel ip.
The one which finally worked was as you can guess rathole. It has a docker image and uses a single config file on both ends. This makes it ideal to use in my current environment. I am still unsure if i want to switch off of cloudflare tunnel but i will definitely switch off playit.gg.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Terraform</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/terraform/</link>
      <pubDate>Tue, 26 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/terraform/</guid>
      <description>&lt;p&gt;One of my big goals with my homelab is resiliency as in that i could lose everything and have the ability to rebuild quickly on a new piece of hardware. To this end i have previously had a gitea repo which contained: a docker compose; a deploy target txt; and a env.sh loader script.
My setup currently looks like a main.ft with indivial files pre container. I am also using a gitea action to run terraform and commit the new tfstate file to the repo. I think this will be able to scale up with me for now once i finish my migration.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Headscale</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/headscale/</link>
      <pubDate>Thu, 17 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/headscale/</guid>
      <description>&lt;p&gt;So in my process of preparing to switch to starlink I setup headscale to replace my wireguard vpn. I thought that I would have to use tailscale as I presumed the headscale server would require a port. It does but it just so happens to use https which I can tunnel with cloudflare. So with that in mind I setup headscale in a docker container and connected my phone with no issue. The server side was slightly harder as a i used the tailscale docker container and accidentally removed the envs so i spent a while trying to figure out why the state file wasn&amp;rsquo;t saving properly. That is fixed now and it works fine.
However on further investigation I realised that I could not use it for my main purpose as cloudflare tunnels do not support web socket PUSH.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pelican</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/pelican/</link>
      <pubDate>Wed, 11 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/pelican/</guid>
      <description>&lt;p&gt;The setup was simple I deployed the panel in a docker container to a fresh docker host. I had to set the application url env to the public url not the private one. Then I installed the wings software on the same VM as the panel. I had to manually copy the config file from the panel. Everything else it automated with gitea actions. I made sure to change some of the files in the config files to my nfs share. Unfortuantly I then ran into a massive bug where I couldn&amp;rsquo;t start any server. I hope this is fixed soon.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Secrets in Vault</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/secrets-in-vault/</link>
      <pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/secrets-in-vault/</guid>
      <description>&lt;p&gt;Since I started storing all my docker compose files in git i have wanted to create a public mirror as a disaster recovery option. To that end i needed a way to remove sensitive envs from the files. To achive this I set the docker env to a shell env like so &lt;code&gt;TEMP: ${TEMP}&lt;/code&gt;
This shell env was set by a script which contained &lt;code&gt;export TEMP=$(vault kv get -field=temp kv/data/docker)&lt;/code&gt;. This vault currently runs as a single node in docker and has to be manually unsealed as needed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mail Server Down</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mail-server-down/</link>
      <pubDate>Thu, 16 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mail-server-down/</guid>
      <description>&lt;p&gt;It started when i tired to set up my emails on Thunderbird mail on arch I noticed it wouldn&amp;rsquo;t connect. I checked the logs and found &amp;ldquo;2025-01-16 21:04:11,919 WARN exited: amavis (exit status 1; not expected)&amp;rdquo; I fixed this relatively quickly by removing &amp;ldquo;amavisd.pid&amp;rdquo;. After this it booted but I still couldn&amp;rsquo;t connect.&lt;/p&gt;
&lt;p&gt;I tracked this down by using dig and whats my ip to see that the dns record was wrong. I fixed this by switching to a cname record set to @ so i only need 1 ddns setup. This finally fixed it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Broken WordPress</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/broken-wordpress/</link>
      <pubDate>Mon, 02 Dec 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/broken-wordpress/</guid>
      <description>&lt;p&gt;I began by trying several plugins to get https working on my website none of the ones I found worked for free so I kept looking until I found one called simple ssl. I installed and activated it but when I went to refresh my website nothing just a plain white screen. I tried lots of different ideas to fix it but nothing worked solutions like renaming plugin and theme folders did nothing in the end I just gave up.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Docker Mailserver</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/docker-mailserver/</link>
      <pubDate>Fri, 22 Nov 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/docker-mailserver/</guid>
      <description>&lt;p&gt;Ever since I setup mailcow I have been annoyed that it runs with docker volumes and updates with a script. This makes it imposible to run how I want. I feel the main benefit of docker should be all the files needed are backed up and I can use the docker compose file to spin the container up anywhere.&lt;/p&gt;
&lt;p&gt;I have tried may times to fix these problems in mailcow and have always failed. So I finally gave up with mailcow and started looking at other options. I quite quickly found docker mailserver as my main option. I don&amp;rsquo;t know if I didn&amp;rsquo;t see it the first time round or if I was scared of by the lack of a GUI. What ever the case now I am happy to use the command line for everything.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Redoing My VPN</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/redoing-my-vpn/</link>
      <pubDate>Tue, 13 Aug 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/redoing-my-vpn/</guid>
      <description>&lt;p&gt;During a backup test I did recently I found that wireguard wasn&amp;rsquo;t working properly. I have no idea how long this has been the case but to fix it I started trying to change the config however when that lead to no improvment I decided to reinstall. This is something I have considered before as my current setup doesn&amp;rsquo;t have a gui which would be nice so I use the repository (&lt;a href=&#34;https://github.com/wg-easy/wg-easy?tab=readme-ov-file&#34;&gt;https://github.com/wg-easy/wg-easy?tab=readme-ov-file&lt;/a&gt;). The install was over all easy however the password hashing didn&amp;rsquo;t work on a super strong password. This seems to be working now and I will probably redo the backup test for wireguard soon.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wazuh File Premissions</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh-file-premissions/</link>
      <pubDate>Mon, 29 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh-file-premissions/</guid>
      <description>&lt;p&gt;I noticed today that Wazuh wasn&amp;rsquo;t working after I restarted my server. I saw in the logs it was failing the bootstrap test. I thought the issue was the mass of file permission error that were appearing before this error showed. However after messing around with file permissions I noticed a error about sysctl vm.max_map_count after running &amp;ldquo;sysctl -w vm.max_map_count=262144&amp;rdquo; it started working however I have no idea how this wasn&amp;rsquo;t a issue until now.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wazuh</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh/</link>
      <pubDate>Mon, 22 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/wazuh/</guid>
      <description>&lt;p&gt;I was originaly planing to try security onion but while reasurching it I came across Wazuh which runs on docker which I always prefer. Once I installed it using a edited version of the compose file in the github repository.&lt;/p&gt;
&lt;p&gt;I managed to install the agent on two of my servers however on my main proxmox host I didn&amp;rsquo;t understand that the server I was the ip of the main host not the server I was installing it on. This lead to a botched install I haven&amp;rsquo;t been able to fix yet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Portainer Docker exec</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/portainer-docker-exec/</link>
      <pubDate>Fri, 19 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/portainer-docker-exec/</guid>
      <description>&lt;p&gt;One day when I tried to use the console section of portainer I got the error &amp;ldquo;Unable to retrieve image details&amp;rdquo;. After looking online I saw that I needed to update portainer so I started looking for the compose file and couldn&amp;rsquo;t find it. Well that was a bit annoying so I ran &amp;ldquo;docker run &amp;ndash;rm -v /var/run/docker.sock:/var/run/docker.sock ghcr.io/red5d/docker-autocompose …&amp;rdquo; which worked as expected. I then pulled the latest image and trimed the compose file. When I removed and restarted the container I was annoyed to see it still wasn&amp;rsquo;t working.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wordpress https</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/wordpress-https/</link>
      <pubDate>Wed, 17 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/wordpress-https/</guid>
      <description>&lt;p&gt;This has for a long time been probably my second biggest issue with my homelab. My main website that your reading this on has been running on http. This happened because i use the domain keldo.uk which is also the domain I use for email. This ment I couldn&amp;rsquo;t route through cloudflare like everything else.&lt;/p&gt;
&lt;p&gt;My original attempt to fix this was with trafik but when I got as far as forwarding the website all I got was a white page. I presumed that nginx proxy manager would be the same however I was proven wrong when I tried today.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ansible Install</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/ansible-install/</link>
      <pubDate>Wed, 10 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/ansible-install/</guid>
      <description>&lt;p&gt;I started by following this video &lt;a href=&#34;https://www.youtube.com/watch?v=NyOSoLn5T5U&#34;&gt;https://www.youtube.com/watch?v=NyOSoLn5T5U&lt;/a&gt;. Once i customised the compose file I managed to setup my first playbook. I decided to store playbooks on my nas for safety and the first one I made was a apt update.&lt;/p&gt;
&lt;p&gt;I then started tinkering with more complicated ones for proxmox and my dns settings. This is still what I am doing as proxmox is working through proxmoxer and if not exactly simple but I am happy with the progress I am making.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Don&#39;t delete random docker Volumes</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/dont-delete-random-docker-volumes/</link>
      <pubDate>Mon, 24 Jun 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/dont-delete-random-docker-volumes/</guid>
      <description>&lt;p&gt;It started when I was trying to install change detection. I was getting a error about not having space on the drive so I decided to delete some unused docker volumes. This lead to a new far more concerning error &amp;ldquo;mkdir /data/compose: no such file or directory&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;After looking online I realised this could be bad so I decided to download a copy of passbolt and then reboot. The first thing I noticed was proxmox stopped working but I realised this was just my dns. The when I did a docker ps it showed that everything was starting fine. However when I went to Portainer it told me to setup a new install.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Broken mailcow</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/broken-mailcow/</link>
      <pubDate>Thu, 30 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/broken-mailcow/</guid>
      <description>&lt;p&gt;I began by trying to move my mailcow install from running on docker volumes to storing data on my nas. I started copying the files however after around the 5th volume I remembered the continers were still online. After I continued even finding a copy of the docker compose.&lt;/p&gt;
&lt;p&gt;However when I ran the compose I got serveral errors about mysql. I realised I had corrupted the mysql database. I tried several edits to the mysql files and failed. After that I went to launch the old copy and realised that was corrupted as well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ICloudpd Notifications</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/storage/icloudpd-notifications/</link>
      <pubDate>Tue, 28 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/storage/icloudpd-notifications/</guid>
      <description>&lt;p&gt;The one feature of Icloudpd that I dislike is the requirement to constantly redo 2fa. I also would have no way of knowing when this is untill I set up one of the notification options.&lt;/p&gt;
&lt;p&gt;I decided since there was no smtp which would be my normal choice I would try out the discord web hook function which I hadn&amp;rsquo;t used before. The setup went fine untill I went to test it I restarted the container and got a notification that it started however, almost strait after that I got a message that it couldn&amp;rsquo;t access the folder that stored my photos. I re aplied the acl which fixed it but I need to find a away to re do the acl on a schedual.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SyncTrayzor</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/storage/synctrayzor/</link>
      <pubDate>Mon, 27 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/storage/synctrayzor/</guid>
      <description>&lt;p&gt;I have been using the default syncthing windows client for a while. However, the task sceudular setup had never worked properly and there for I had been forced to run it manually every now and then.&lt;/p&gt;
&lt;p&gt;Luckily I came across a reddit post that mentionted SyncTrayzor at first I thought it was a different software but then I found out it worked with my existing syncthing server. I downloaded the installer and ran it. It worked even better than expected as it managed to use my existing config with the only change needed was to add an allow newer config flag in the settings.&lt;/p&gt;</description>
    </item>
    <item>
      <title>iCloudpd</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/storage/icloudpd/</link>
      <pubDate>Fri, 10 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/storage/icloudpd/</guid>
      <description>&lt;p&gt;I wanted to try and find a better way to backup my photos from my iPhone to my NAS. I had been using Nextcloud with the app on my phone to do this however is was slow and nextcloud pritiy much always ran so slow a page could take around 60 seconds to load.&lt;/p&gt;
&lt;p&gt;I had seen iCloudpd before as a application on TrueNAS and so wanted to try it out. I set up a docker compose and signed in. However I then started getting a message to create the .mounted file which I had already done. This prity much instantly told me that there was somthing wrong with my mount. However when I looked it all seemed fine so I was forced to ssh in and relook at the new mount I had made to my NAS. After some failed ideas I noticed that the mount only had empty folders in it. This finaly reminded me that my Photos folder was acutualy a dataset so I switched the nsf share to that and it started to run a backup.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Passbolt update</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/passbolt-update/</link>
      <pubDate>Mon, 06 May 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/passbolt-update/</guid>
      <description>&lt;p&gt;I began to notice issues when my passwords in the ios passbolt app when it was&amp;rsquo;t showing my passwords. I quickly found a range of posts about historical issues with ios 17 batas but as far as I could see they had been solved in app version 15 and I was on 18.&lt;/p&gt;
&lt;p&gt;The next step I took was to run the health check this found that I had two issues: my install didn&amp;rsquo;t force https which is fine because if uses cloudflare; and my install was very out of date. Updating is one of the big draw backs of docker in my opinion and while there was a page about updating on the passbolt website I decided to just figure it out through portainer.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mailcow ssl</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-ssl/</link>
      <pubDate>Sat, 13 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-ssl/</guid>
      <description>&lt;p&gt;The first thing I noticed was wrong was that my Iphone was giving me a pop up telling me it could verify the identity of mail.keldo.uk. My first though was that the ssl cert had expired but as far as I knew Mailcow should automaticly refresh the cert. Luckily it was easy to debug as Mailcow has a nice selection of logs and I just open the acme logs and Imedialty saw the issue &amp;ldquo;mail.keldo.uk - Found AAAA record for mail.keldo.uk: 2a00:23c7:82c2:6401:be24:11ff:fe6d:10fa - skipping A record check&amp;rdquo; was apearing every hour. I setup ipv6 records when I set up mailcow however since I have a dynamic IP and haven&amp;rsquo;t set up a ddns for ipv6 it was seeing ipv6 skiping ipv4 and then seeing the ipv6 didn&amp;rsquo;t match. The simple solution was I just removed the ipv6 record and then the next hour it was fixed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Metasploitable 2</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/metasploitable-2/</link>
      <pubDate>Fri, 05 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/security/metasploitable-2/</guid>
      <description>&lt;p&gt;For a addition to my cyber security home lab I added a metasploitable VM. I made a VM with weak specs (but it should be fine) and then downloaded, unziped and converted it then just added it to the VM. I made sure to put it in VLAN 30 then booted it launched and I could access the UI. I look forward to practising with this.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kiwix</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/kiwix/</link>
      <pubDate>Thu, 04 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/kiwix/</guid>
      <description>&lt;p&gt;I began by changing the command to a docker compose it was easy apart from a random *.zim that was at the end. I just skipped over it and presumed it would be fine but there was no url so I thought I needed a zim for it to share so I downloaded all of Wikipedia which took around 1 hour so not to bad but after a restart there was still no page. I returned to that random &lt;em&gt;.zim and after some googling and trial and error I found I needed to add the line &amp;ldquo;command: &amp;lsquo;&lt;/em&gt;.zim&amp;rsquo;&amp;rdquo; after that it worked fine and I added ask Ubuntu as well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Recoved WP db</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/recoved-wp-db/</link>
      <pubDate>Mon, 01 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/recoved-wp-db/</guid>
      <description>&lt;p&gt;I started by spinning up phpmyadmin I didn&amp;rsquo;t care about the settings as I was only going to use it for a bit. At first i tried moving files 1 by 1 but when that gave error I moved all the files I had in my mount and tried to login it said my login was wrong so I tried my wordpress login which worked. I navigated to the pages table and was horrified to see it only have 4 rows. As a last hope I restored a older copy of the db I had from just after the fail. When I checked this time there were 159 posts and a quick check showed I was all there!!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Nextcloud</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/nextcloud/</link>
      <pubDate>Mon, 12 Feb 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/documents/nextcloud/</guid>
      <description>&lt;p&gt;Today I installed nextcloud through docker I&amp;rsquo;m using the Linux server image and the install was very smooth however when I got to the web UI it was slow and I mean anywhere from 5 seconds to 60 per click! But I continued thinking it was just running a background install and would soon speed up.&lt;/p&gt;
&lt;p&gt;I added my NAS as external storage which worked fine and then setup the recognize app which is basically facial regognision like your phone does where it groups the same people and lets you name them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mailcow Install</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-install/</link>
      <pubDate>Sat, 13 Jan 2024 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/mail/mailcow-install/</guid>
      <description>&lt;p&gt;I decided I wanted to be able to get emails from my services as that is the mail method most of them support. For my mail server i decided to use mailcow rather than try to stitch together my own group of programs. The install was easy with no errors by simply just using a Docker compose file. Its smtp work fine with TrueNAS, Pterodactyl, Nextcloud, Proxmox and Passbolt however i could not get it working with Mealie.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pi Hole</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/pi-hole/</link>
      <pubDate>Thu, 28 Dec 2023 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/managment/pi-hole/</guid>
      <description>&lt;p&gt;I chose to use Pi hole for ad blocking and local dns as it has a large community and I have used it in the past. The install went fine and then i used &lt;a href=&#34;http://firebog.net&#34;&gt;http://firebog.net&lt;/a&gt; to get a list of ad blocks. The only issues I have run into is that I blacklisted a google link that stopped a lot of surchs i did and that it only prompts you to re loggin after you fail to do something.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Docker Install</title>
      <link>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/docker-install/</link>
      <pubDate>Wed, 27 Dec 2023 00:00:00 +0000</pubDate>
      <guid>https://keldo.uk/server/proxmox/vms/docker-hosts/docker/docker-install/</guid>
      <description>&lt;p&gt;I began by creating a VM and adding a nfs share however my first attempt I installed Docker with the Ubuntu installer this lead to a wide range of problems so justed deleted the VM and started again. On my next attempt I made sure to only install docker after using apt install. I managed to get Portainer to work first try and then just had to move my old containers off my PC, this was not to bad as i just moved the files to the network share and then translated the compose files to the Portainer container options (I later found out that i could do it with docker compose files and switched most of them to that).
&lt;img loading=&#34;lazy&#34; src=&#34;Pasted%20image%2020250604153705.png&#34;&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
