Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
docker_notes:docker-dhcp [2025-06-08 Sun wk23 19:33] – [main dhcp4] baumkpdocker_notes:docker-dhcp [2025-06-08 Sun wk23 19:34] (current) – [main dhcp4] baumkp
Line 79: Line 79:
 I had a problem when upgrading to to Kea 2.6.0 that stopped kea-dhcp4 operating with an error ''file: /etc/kea/kea-dhcp4.conf, reason: subnet configuration failed: missing parameter ‘id’''.  The error also reported the configuration line where the missing parameter was expected.  Adding the missing parameter to the file as per Kea docs [[https://kea.readthedocs.io/en/kea-2.6.0/arm/dhcp4-srv.html#ipv4-subnet-identifier|ipv4-subnet-identifier]] resolved this error.  Apparently this parameter was auto assigned in earlier versions of Kea, if not manually assigned in configuration file.  In Kea version 2.6.0 manual assignment became mandatory, see [[https://kb.isc.org/docs/changes-to-be-aware-of-when-migrating-to-kea-2-6-0|Changes to Be Aware of When Migrating to Kea 2.6.0]].++++ I had a problem when upgrading to to Kea 2.6.0 that stopped kea-dhcp4 operating with an error ''file: /etc/kea/kea-dhcp4.conf, reason: subnet configuration failed: missing parameter ‘id’''.  The error also reported the configuration line where the missing parameter was expected.  Adding the missing parameter to the file as per Kea docs [[https://kea.readthedocs.io/en/kea-2.6.0/arm/dhcp4-srv.html#ipv4-subnet-identifier|ipv4-subnet-identifier]] resolved this error.  Apparently this parameter was auto assigned in earlier versions of Kea, if not manually assigned in configuration file.  In Kea version 2.6.0 manual assignment became mandatory, see [[https://kb.isc.org/docs/changes-to-be-aware-of-when-migrating-to-kea-2-6-0|Changes to Be Aware of When Migrating to Kea 2.6.0]].++++
  
-++++Upgrade problems from 2.6.2 to 2.6.3 Kea as yet again broken or perhaps enforce configuration backwards compatibility, TL;DR;|+++++Upgrade problems from Kea 2.6.2 to 2.6.3, yet again broken or perhaps enforced configuration backwards compatibility, TL;DR;|
 The socket files **must** now be in ''/run/kea'' and directory permission must be set to 750. The socket files **must** now be in ''/run/kea'' and directory permission must be set to 750.
  
-I previously used a general docker volume director directive to place all my configuration files into /app and then configured from there as require. +I previously used a general docker volume director directive to place all my configuration files into /app and then configured from there as required. 
     #"name": "/app/kea.leases4.csv",     #"name": "/app/kea.leases4.csv",
     #Kea 2.6.3 requires /var/lib/kea     #Kea 2.6.3 requires /var/lib/kea