Release v1.2.1 Latest

Latest

Compare

Choose a tag to compare

Release v1.2.0

Compare

Choose a tag to compare

provisioning: add user field to container step

Add a `user` field on the container provisioning step that overrides
the user the container's command runs as. Plumbs through to
containerapi.WithUser, equivalent to `docker run --user`. Accepts a
numeric uid, uid:gid, or a name from the image's /etc/passwd; an empty
value keeps the image default.

Useful with execution-environment images (e.g. anything built by
ansible-builder) that default to a non-root uid: virter binds the SSH
key under /root/.ssh, which such users cannot read, so setting
`user = "0"` works as a workaround.

Release v1.1.0

Compare

Choose a tag to compare

⚠️ v1.0.0 introduces a few breaking changes against v0.x.

See the migration guide to learn more.

🚀 Release v1.0.0

Compare

Choose a tag to compare

⚠️ Breaking Changes in this release

• --pull-policy flag removed: The deprecated --pull-policy flag was removed from vm run and image build. Use --vm-pull-policy instead.

• --bootcapacity / --bootcap deprecated: Renamed to --boot-capacity for consistency. The old flags still work but print a deprecation warning and will be removed in a future release.

• Unknown keys in provisioning files are now errors: Previously, unknown TOML keys in provisioning files produced a warning. Now they cause a hard error. This catches typos (e.g. destination instead of dest) but will break any provisioning files that relied on extra/misspelled keys being silently ignored.

• Provisioning filesystem access restricted to working directory: rsync.source paths and container.copy.dest paths in provisioning steps are now validated to be within the current working directory. Provisioning files that reference paths outside the working directory (e.g. absolute paths like /etc/... or paths that escape via ../) will now fail.

Release v0.30.0

Compare

Choose a tag to compare

build(deps): bump github.com/spf13/viper from 1.20.0 to 1.20.1

Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.20.0 to 1.20.1.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/[email protected])

Release v0.29.0

Compare

Choose a tag to compare

check for nil desc.Metadata before attempting to unmarshall, avoiding…

… a segfault for non-virter VMs (#33)

Release v0.28.1

Compare

Choose a tag to compare

If 'truncate' fails for /etc/machine-id during 'commit', attempt with…

… 'sudo' before giving up

If 'truncate' fails for /etc/machine-id, attempt with 'sudo' before giving up (#29). Also, fix a spelling error in the help messages.

Release v0.28.0

Compare

Choose a tag to compare

Release v0.27.0

Compare

Choose a tag to compare

virter: pass-through exit code from provisioning

When a provisioning step fails, it may be helpful to the caller of
virter to know the exit code of the script.

So, if an SSH or container provisioning step fails with an exit code,
pass it through to the CLI, exiting from the virter process with the
same exit code.

Release v0.26.0

Compare

Choose a tag to compare