Skip to content

Instantly share code, notes, and snippets.

@reytech-dev
reytech-dev / Fix.md
Last active November 20, 2025 20:36
ZONE_CONFLICT: 'docker0' already bound to a zone
  1. Check if docker zone exists in firewall-cmd
$ firewall-cmd --get-active-zones
  1. If "docker" zone is available, change interface to docker0 (not persisted)
$ sudo firewall-cmd --zone=docker --change-interface=docker0
  1. If "docker" zone is available, change interface to docker0 (persisted, thanks rbjorklin)
global:
hosts:
domain: vcs.services.kubernetes
externalIP: 192.168.56.101
ingress:
configureCertmanager: false
annotations:
kubernetes.io/ingress.class: "nginx"
cert-manager.io/cluster-issuer: "ca-issuer"
shell:
global:
edition: ee
serviceAccount:
enabled: true
create: true
annotations:
name: "gitlab-sa"
eks.amazonaws.com/role-arn: "${gitlab_s3_iam_role}"
iam.amazonaws.com/role: "${gitlab_s3_iam_role}"
ingress:
@fardjad
fardjad / considerations-for-running-postgres-on-nfs.md
Last active January 25, 2026 19:16
[Considerations for Running Postgres on NFS] Considerations for running a Postgres database on an NFS share #blog #postgres #nfs #fsync #fsexport #mount

Considerations for Running Postgres on NFS

Background

Over the weekend, I decided to try running a Postgres database in my Homelab. In my current setup, the most convenient option for storage is NFS. However, NFS is especially tricky for databases. A misconfigured setup can lead to performance or data corruption issues.

After watching