vyos-1x.git/src/op_mode/container.py, branch fix/T8955-http-api-verify-tls

T8410: Fix typos and mistakes for operational and configuration commands

2026-03-24T17:02:56+00:00

Fix typos and mistakes in the commands and comments No functional changes

op-mode: T8018: disable buffered output when adding container images

2026-02-02T20:30:42+00:00

container: T7305: fix VRF loss when restarting pods

2025-11-03T20:09:14+00:00

Container networks are only started when there is at least one active consumer. If a network is created without any attached containers, it does not need to be assigned to a VRF yet. When the last container in a pod is stopped, its associated container network is removed. Upon container restart, the kernel recreates the network, but the VRF assignment may be lost in the process. This change ensures that all container networks are correctly reattached to their designated VRFs when a pod restarts.

T7957: filter stderr when deleting container images

2025-10-25T14:38:54+00:00

The call to rc_cmd('podman inspect ...') determines whether a container image scheduled for deletion has any ancestor containers still using it. Previously, if the podman command wrote output to stderr, rc_cmd() would return that error message alongside or instead of the ancestor container ID. This caused subsequent podman calls to fail, as the error string was incorrectly treated as a valid command argument. This change ensures only valid ancestor IDs are returned. This is a fix for commit a99ca6d11b5 ("op-mode: T7403: add option for forcefully remove a container image")

container: T6673: Fix restart of containers with podman (#4691)

2025-09-18T14:14:55+00:00

Fixed issue with podman and systemd sync when restarting containers with 'podman restart' command. - Placed podman storage directory in vyos/defaults.py - Replaced repeated declarations with vyos.defaults.directories['podman_storage']

op-mode: T7403: fix image deletion when a single image ID is provided

2025-07-31T18:26:11+00:00

Commit a99ca6d11 ("op-mode: T7403: add option for forcefully removing a container image") did not account for the case where a single image ID is passed as a string. This led to incorrect behavior during iteration. Without converting the string to a list, the code iterates over individual characters of the image ID rather than treating it as a single item. As a result, the system attempts to delete non-existent container images based on these characters.

op-mode: T7403: add option for forcefully remove a container image

2025-07-29T20:15:09+00:00

If you have multiple images (tags) loaded for a container which point to the exact same hash - you can only forcefully delete them. vyos@vyos:~$ delete container image 70dc5806 Error: unable to delete image "70dc5806" by ID with more than one tag ([registry.io/foo/bar:v1.0 registry.io/foo/bar:v1.0.1]): please force removal In additon an image that is still beeing used can not be removed from the system as this would cause infinite container restarts. vyos@vyos:~$ delete container image all force Cannot delete image "d205499ae8bb" because it is currently being used by container "3b290f90e83d"!

op-mode: T7403: print STDOUT when adding a container image

2025-07-29T20:14:54+00:00

T7591: remove copyright years from source files

2025-06-28T21:16:52+00:00

The legal team says years are not necessary so we can go ahead with it, since it will simplify backporting. Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \ 's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors /g' In addition we will error-out during "make" if someone re-adds a legacy copyright notice

container: T7473: fix show/monitor container log failed when log-driver is journald

2025-06-17T15:02:07+00:00