This update for conmon, fuse-overlayfs, libcontainers-common, podman fixes the following issues:
podman was updated to v2.0.6 (bsc#1175821)
fix install location for zsh completions
Update to v2.0.6:
Features
Changes
Bugfixes
API
Change hard requires for AppArmor to Recommends. They are not needed for runtime or with SELinux but already installed if AppArmor is used [jsc#SMO-15]
Update to v2.0.4
Fixed a bug where the CgroupVersion field in responses from the compat Info endpoint was prefixed by 'v' (instead of just being '1' or '2', as is documented).
Suggest katacontainers instead of recommending it. It's not enabled by default, so it's just bloat
Update to v2.0.3
pod inspectpod inspectUpdate to podman v2.0.2
libpod.GetEvents(...)podman mount didn't error as rootlesssystem servicenilsystem service panic from early hangup in eventsps for ctrs sharing networkStatusCreated from volume creation/json from compat network EPspodman auto update.rm executableUpdate to podman v2.0.0
podman generate systemd command now supports the --new
flag when used with pods, allowing portable services for pods
to be created.podman play kube command now supports running Kubernetes
Deployment YAML.podman exec command now supports the --detach flag to
run commands in the container in the background.-p flag to podman run and podman create now supports
forwarding ports to IPv6 addresses.podman run, podman create and podman pod create
command now support a --replace flag to remove and replace any
existing container (or, for pod create, pod) with the same name--restart-policy flag to podman run and podman create
now supports the unless-stopped restart policy.--log-driver flag to podman run and podman create
now supports the none driver, which does not log the
container's output.--mount flag to podman run and podman create now
accepts readonly option as an alias to ro.podman generate systemd command now supports the --container-prefix,
--pod-prefix, and --separator arguments to control the
name of generated unit files.podman network ls command now supports the --filter
flag to filter results.podman auto-update command now supports specifying an
authfile to use when pulling new images on a per-container
basis using the io.containers.autoupdate.authfile label.podman exec command would log to journald
when run in containers loggined to journald
(#6555).podman auto-update command would not
preserve the OS and architecture of the original image when
pulling a replacement
(#6613).podman cp command could create an extra
merged directory when copying into an existing directory
(#6596).podman pod stats command would crash
on pods run with --network=host
(#5652).podman network inspect and
podman network rm commands did not properly handle non-default
CNI configuration paths (#6212).podman inspect would sometimes incorrectly
report the network mode of containers started with --net=none.conmon
is killed before the container it is monitoring.Update to podman v1.9.3:
Update podman to v1.9.1:
Bugfixes
Update podman to v1.9.0:
Features
Changes
Bugfixes
HTTP API
Misc
Add 'systemd' BUILDFLAGS to build with support for journald logging (bsc#1162432)
Update podman to v1.8.2:
Features
Bugfixes
HTTP API
Update podman to v1.8.1:
Features
Bugfixes
HTTP API
Misc
Configure br_netfilter for podman automatically (bsc#1165738) The trigger is only excuted when updating podman-cni-config while the command was running
conmon was update to v2.0.20 (bsc#1175821)
Add --no-sync-log option to instruct conmon to not sync the logs of the containers upon shutting down. This feature fixes a regression where we unconditionally dropped the log sync. It is possible the container logs could be corrupted on a sudden power-off. If you need container logs to remain in consistent state after a sudden shutdown, please update from v2.0.19 to v2.0.20
Update to v2.0.17:
Update to v2.0.16:
Enable support for journald logging (bsc#1162432)
Update to v2.0.15:
Update to v2.0.14:
Update to v2.0.12
Update to v2.0.11
fuse-overlayfs was updated to 1.1.2 (bsc#1175821):
libcontainers-common was updated to fix:
Update storage to 1.20.2
Remove remaining difference between SLE and openSUSE package and ship the some mounts.conf default configuration on both platforms. As the sources for the mount point do not exist on openSUSE by default this config will basically have no effect on openSUSE. (jsc#SLE-12122, bsc#1175821)
Update to image 5.4.4
Remove the /var/lib/ca-certificates/pem/SUSE.pem workaround again. It never ended up in SLES and a different way to fix the underlying problem is being worked on.
Add registry.opensuse.org as default registry [bsc#1171578]
Add /var/lib/ca-certificates/pem/SUSE.pem to the SLES mounts. This for making container-suseconnect working in the public cloud on-demand images. It needs that file for being able to verify the server certificates of the RMT servers hosted in the public cloud. (https://github.com/SUSE/container-suseconnect/issues/41)
This update was imported from the SUSE:SLE-15-SP1:Update update project.