VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=circinus-public-unmaintained 2024-04-02T22:15:43+00:00 2024-04-02T22:15:43+00:00 Christian Breunig christian@breunig.cc 2024-04-02T22:15:43+00:00 urn:sha1:274b2da242acd1f1f64ff1dee471e34295137c5f found using "git ls-files *.py | xargs pylint | grep W0611" 2024-02-27T21:20:41+00:00 Christian Breunig christian@breunig.cc 2024-02-27T21:20:41+00:00 urn:sha1:bfc065f2c4dcfc969981453e49b8156330674006 The current VyOS container image manipulation "delete container image" command allows force removal of container images - even if they still have a container running. Drop the --force option from the op-mode script. vyos@vyos:~$ delete container image 2636705a815a Error: image used by 6adb0175d47f.. image is in use by a container: consider listing external containers and force-removing image 2024-02-24T09:27:26+00:00 Christian Breunig christian@breunig.cc 2024-02-24T09:27:26+00:00 urn:sha1:52df4d62074a76eb173931c5fbaf5a4e22d6e346 container: T6060: support removing all container images at once via op-mode 2024-02-24T08:32:54+00:00 Christian Breunig christian@breunig.cc 2024-02-24T08:25:42+00:00 urn:sha1:9e51a1661fac3e0d762cffdd28705e7e4bad76e9 cpo@LR1.wue3:~$ show container image REPOSITORY TAG IMAGE ID CREATED SIZE docker.io/library/busybox latest 3f57d9401f8d 5 weeks ago 4.5 MB docker.io/jacobalberty/unifi v7.5 f6df690d6c67 4 months ago 827 MB docker.io/jacobalberty/unifi v7.4 7838b75ef7b9 7 months ago 786 MB cpo@LR1.wue3:~$ delete container image Possible completions: 3f57d9401f8d Delete container image 7838b75ef7b9 all f6df690d6c67 cpo@LR1.wue3:~$ delete container image all cpo@LR1.wue3:~$ show container image REPOSITORY TAG IMAGE ID CREATED SIZE 2024-02-24T08:07:17+00:00 Christian Breunig christian@breunig.cc 2024-02-23T20:49:50+00:00 urn:sha1:baf30d8319ef4d0f0cc4cdf0f7c12f03f8a492b6 It does not make sense to perform the "podman login" command when setting up containers, as images are not automatically pulled in from the registry - due to issues with the default route during startup. The same issue manifests in "podman login" where we can not login to a registry unless there is a default route present. This commit changes the behavior that the container registry is part of the configuration, but it is only referenced during "add container image" and thus never during system boot. 2023-07-14T20:18:36+00:00 Christian Breunig christian@breunig.cc 2023-07-14T20:18:36+00:00 urn:sha1:d1ca536da448749dff557f13ecae97b124026e96 * T5195: move run, cmd, call, rc_cmd helper to vyos.utils.process * T5195: use read_file and write_file implementation from vyos.utils.file Changed code automatically using: find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import read_file$/from vyos.utils.file import read_file/g' {} + find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import write_file$/from vyos.utils.file import write_file/g' {} + * T5195: move chmod* helpers to vyos.utils.permission * T5195: use colon_separated_to_dict from vyos.utils.dict * T5195: move is_systemd_service_* to vyos.utils.process * T5195: fix boot issues with missing imports * T5195: move dict_search_* helpers to vyos.utils.dict * T5195: move network helpers to vyos.utils.network * T5195: move commit_* helpers to vyos.utils.commit * T5195: move user I/O helpers to vyos.utils.io 2023-06-21T21:17:27+00:00 Christian Breunig christian@breunig.cc 2023-06-21T20:11:05+00:00 urn:sha1:69ce448cbb02be5c29f6420dc91618639ec30301 2023-02-09T06:31:40+00:00 Christian Breunig christian@breunig.cc 2023-02-09T06:31:40+00:00 urn:sha1:f234b602c4b0554456c494451b438d32f3386d69 This reverts commit b17251334c57c2f6875c19ad4e6c6127aa9e1811. 2023-01-30T09:03:15+00:00 Zen3515 7106408+Zen3515@users.noreply.github.com 2023-01-30T08:58:11+00:00 urn:sha1:b17251334c57c2f6875c19ad4e6c6127aa9e1811 2023-01-09T21:39:37+00:00 John Estabrook jestabro@vyos.io 2023-01-09T20:42:06+00:00 urn:sha1:f440fbc9ba9019b25fb9f059357052701d990ef3 Encapsulating the add/delete image commands in the op-mode script allows automatic generation of corresponding API schema definitions.