Changes between 5.2.0 and 5.3.0
Added:reloadcommand toappjail-dnsrc script:- One problem I've often encountered when deploying multiple jails with a tool like Director is that, from time to time, one service may depend on another, and it's very convenient to use hostnames instead of IPv4 addresses. The problem is that
appjail-dnsreloads itshosts(5)file after a certain amount of time (60seconds by default), which is undesirable for services that require a hostname to be available immediately. A workaround is to set theaddresssuboption within thevirtualnetoption when usingappjail-quick(1)(or any command that uses it, such asappjail-oci(1),appjail-makejail(1), etc.), which reserves an IPv4 address, but this isn’t as convenient as a simple hostname. - This command is called after a jail reserves an IPv4 address when using Virtual Networks only if
appjail-dnsis enabled.
- One problem I've often encountered when deploying multiple jails with a tool like Director is that, from time to time, one service may depend on another, and it's very convenient to use hostnames instead of IPv4 addresses. The problem is that
Added:dependoption toappjail-quick(1).- Improvements for container destruction:
- Attempt to destroy the container only if it exists.
- In
share/appjail/lib/oci:oci_check_container(), the check command has been improved to use a filter in buildah andgrep(1).grep(1)was necessary because (in theory) the filter may match more than one container. This makesshare/appjail/lib/oci:oci_get_container_info()function unnecessary, so it is removed.
Added: missing word in phrase when the OS can't be detected reliably inshare/appjail/lib/oci:oci_get_osversion().- Attempt to destroy the container before (re)creating it:
- If the user, or even a process (such as Director, which is non-interactive by nature and is used primarily in conjunction with Overlord), stops the jail midway through the process, the container will remain unused, and when the jail is recreated, an error will occur indicating that the container already exists, forcing the user to manually destroy the container, which is undesirable in these contexts.
Improved:EntrypointandCmdhandling inappjail-oci(1)(letjqhandle this and shell-escaping).
Full Changelog: v5.2.0...v5.3.0