Stein Series Release Notes¶
4.5.0¶
New Features¶
When deploying with Podman, we can disable the container healthchecks by using paunch apply –healtcheck-disabled.
paunch learns ‘hostname’ wich maps to podman run –hostname and ‘extra_hosts’ mapping to podman run –add-host.
4.3.0¶
New Features¶
Add new “cont_log_path”. It must point to a directory, where the container engine will puts logs issued from containers standard output. It works only for podman.
Add new “–container-log-path” allowing to actually set cont_log_path from the CLI call directly.
Podman is now the default container runtime, replacing Docker.
Adds a new systemd_exec_flags parameter for paunch-managed systemd unit
Deprecation Notes¶
Docker runtime is deprecated in Stein and will be removed in Train.
4.2.0¶
New Features¶
Add –memory=x option for the action run a container. This allows setting constraints on max memory usage, which is memory.limit_in_bytes in memory cgroup. Also added –memory-swap and –memory-swappiness options to control swap settings.
Deprecation Notes¶
The default_runtime ABI parameter is deprecated, use cont_cmd instead. The default-runtime CLI argument retains unchanged.
Bug Fixes¶
Fixed
--labelscan takes multiple values.
4.1.0¶
Other Notes¶
Logging verbosity and destination file can be controled with
--debug--verboseand--log-file.
4.0.0¶
New Features¶
For all containers managed by podman, we’ll create a systemd unit file so the containers automatically start at boot and restart at failure. When the container is removed, we’ll disable and stop the service, then remove the systemd unit file. We prefix the SystemD service so we can identify them better. It will help to not conflict when rpms are installed on the host and have the same service name as their container name. For example haproxy rpm and haproxy container would have the same service name so the prefix will help to not having this conflict when removing the rpms during a cleanup by the operator.
