diff options
| -rw-r--r-- | NEWS | 23 | ||||
| -rw-r--r-- | vmdb/plugins/unpack_rootfs_plugin.py | 4 | ||||
| -rw-r--r-- | vmdb/version.py | 4 | ||||
| -rw-r--r-- | vmdb2.md | 7 |
4 files changed, 35 insertions, 3 deletions
@@ -5,6 +5,29 @@ Project is now in "selfish maintenance mode". I make changes when I need them for myself, but I'm not developing new features otherwise. I will review and merge patches, though. +Version 0.40, released 2024-03-23 +----------------------------------------------------------------------------- + +Version number is bumped a lot to avoid some incorrectly tagged +versions that Lars is very sorry for. Other than that, this version is +mainly a few bug fixes, mostly from other people. + +* Documentation fix: `README.md` points to `base.vmdb` as an example, + rather than `pc.vmdb`, which has long since been deleted. + +* `ppc64el.vmdb` has been fixed so that it at least builds. It's + unknown whether it builds an image that boots. + +* From Matej Kovac, fixes to `resolv.conf` configuration: don't copy + the host's configuration. + +* From Peter Palfrader, a fix the `cryptsetup` plugin to import the + `logging` module. + +* From Victor Westerhuis, a fix to using the right `grub-ieee1275` + depending on the target system. + + Version 0.28, released 2023-08-02 ----------------------------------------------------------------------------- diff --git a/vmdb/plugins/unpack_rootfs_plugin.py b/vmdb/plugins/unpack_rootfs_plugin.py index dc67c01..005959f 100644 --- a/vmdb/plugins/unpack_rootfs_plugin.py +++ b/vmdb/plugins/unpack_rootfs_plugin.py @@ -38,7 +38,9 @@ class UnpackCacheStepRunner(vmdb.StepRunnerInterface): tar_path = settings["rootfs-tarball"] logging.debug(f"tar_path: {tar_path!r}") if not tar_path: - raise Exception("--rootfs-tarball MUST be set") + raise Exception( + "--rootfs-tarball MUST be set if using the 'unpack-rootfs' step" + ) if os.path.exists(tar_path): vmdb.runcmd(["tar", "-C", rootdir, "-xf", tar_path, "--numeric-owner"]) state.rootfs_unpacked = True diff --git a/vmdb/version.py b/vmdb/version.py index 3a848b2..7bdba64 100644 --- a/vmdb/version.py +++ b/vmdb/version.py @@ -1,2 +1,2 @@ -__version__ = "0.28" -__version_info__ = (0, 28) +__version__ = "0.40" +__version_info__ = (0, 40) @@ -140,6 +140,13 @@ Due to the kinds of things vmdb2 does (such as mounting, creating device nodes, etc), it needs to be run using root privileges. For the same reason, it probably can't be run in an unprivileged container. +Running vmdb2 in a container, privileged or not, is not supported. If +it works, that is a happy accident. There are no tests to make sure +that works, however, and no patches to make vmdb2 work in a container +will be considered for merging. This is because vmdb2 is maintained by +Lars, who has no use for containers, and does not want the maintenance +burden of having code that supports that. + ## Setting the hostname |