Releases: containers/netavark
Releases · containers/netavark
v1.9.0
v1.8.0
- iptables: improve error when ip6?tables commands are missing
- docs: Convert markdown with go-md2man instead of mandown
- iptables: drop invalid packages
- bump rust edition to 2021
- Add ACCEPT rules in firewall for bridge network with internal dns
- Add vrf support for bridges
Update 2023-09-28:
replaced netavark-v1.8.0-vendor.tar.gz tarball with working one (#819)
v1.7.0
v1.5.1
v1.6.0
v1.5.0
v1.4.0
v1.3.0
- Housekeeping and code cleanup
- macvlan: remove tmp interface when name already used in netns
- Add support for route metrics
- netlink: return better error if ipv6 is disabled
- macvlan: fix name collision on hostns
- Ignore dns-enabled for macvlan (BZ2137320)
- better errors on teardown
- allow customer dns servers for containers
- do not set route for internal-only networks
- do not use ipv6 autoconf
v1.2.0
v1.1.0
v1.1.0
This tag was signed with the committer’s verified signature.
The key has expired.
mheon
Matt Heon
- Netavark is now capable of starting Aardvark on a port other than 53 (controlled by dns_bind_port in containers.conf). Firewall rules are added to ensure DNS still functions properly despite the port change.
- Added the ability to isolate networks. Networks with the isolate option set cannot communicate with other networks with the isolate option set.
- Improved the way Aardvark is launched to avoid potential race conditions where DNS would not be ready when containers were started.
- Fixed a bug where Aardvark could not be run in environments with a read-only /proc (e.g. inside a container).