Releases: dfr/ocijail
Releases · dfr/ocijail
v0.6.0
v0.5.1
v0.5.0
What's Changed
- Add support for the
featurescommand - Improved error handling for jail syscalls
- Improve handling of failures to execute a container's start command.
- Add support for ip4.addr and ip6.addr parameters for non-vnet jails by @vgrebenschikov in #10
- Add returning JID as part of ocijail state by @vgrebenschikov in #11
- create: support allow.* jail parameters via OCI annotations by @ahze in #12
New Contributors
- @vgrebenschikov made their first contribution in #10
- @ahze made their first contribution in #12
Full Changelog: v0.1.1...v0.5.0
v0.4.0
v0.3.0
- Label container mounts with MNT_IGNORE to reduce clutter from df output.
- Ignore EINVAL when cleaning up container mounts - this can happen when a previous attempt to delete the container failed for some reason.
- Clean up partial state directories in delete - this also helps to clean up after a previous failed delete.
- Add a list command (inspired by crun) to add visibility of container state.
- Allow entrypoint paths which are relative to the process current working directory. This idiom is used by democratic-csi.
v0.2.0
- Fixes for integration tests
- Resolve symbolic links in the container namespace when processing mounts
- Implement support for read-only container root
- Add an annotation to control whether the container creates a new vnet or inherits one from a parent jail
- Allow delete for containers in states other than 'stopped' for compatiblity with crun and runc.
v0.1.1
v0.1
Several changes from v0.1rc2 including:
- Support for mounting files into containers on FreeBSD-13.2 and later
- Support for the cri-o container engine
- Add an experimental mount pseudo-option to support adding and removing entries from the container's devfs
- Fixes to enable 'podman restart -a' after a host reboot