aboutsummaryrefslogtreecommitdiff
path: root/net/netavark/Makefile
Commit message (Collapse)AuthorAge
* rust: Consolidate cargo environment variablesJeffery To2023-10-11
| | | | | | | | | | | | | | | | | | | | | | | This consolidates all environment variables for cargo into: * CARGO_HOST_CONFIG_VARS / CARGO_PKG_CONFIG_VARS These contain all cargo-specific environment variables, i.e. without "common" variables like CC. * CARGO_HOST_VARS / CARGO_PKG_VARS (renamed from CARGO_VARS) These contain all environment variables to be passed to cargo. This also: * Set the CARGO_BUILD_TARGET environment variable instead of using the --target command-line option * Update Python include files to use CARGO_HOST_CONFIG_VARS / CARGO_PKG_CONFIG_VARS Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* netavark: update to 1.8.0Oskari Rauta2023-10-02
| | | | | | | | | | | | changelog: - 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 Signed-off-by: Oskari Rauta <oskari.rauta@gmail.com>
* netavark: update to 1.7.0Oskari Rauta2023-09-16
| | | | | | Changelog: https://github.com/containers/netavark/compare/v1.6.0...v1.7.0 Signed-off-by: Oskari Rauta <oskari.rauta@gmail.com>
* netavark: update to v1.6.0Oskari Rauta2023-06-12
| | | | | | | | | | | | | netavark v1.6.0 was released, so instead of using git version, use release. Does not contain very much of changes, but list is available from netavark's commit log. Software now comes with additional tool named netavark-dhcp-proxy-client which is now included in package. Signed-off-by: Oskari Rauta <oskari.rauta@gmail.com>
* netavark: add new packageOskari Rauta2023-05-14
podman is moving from cni to netavark. Netavark supports currently only iptables, so I was in touch some time ago with mainstream maintainer and provided a "none" firewall driver - to make it possible to use netavark without firewalling features. Driver cannot be selected at this time without environment variable that selects it, so I made a config file for openwrt and a wrapper script that takes advantage of it. Available options are iptables, nftables and none - but selecting nftables just tells user that nftables isn't yet supported. firewall "none" driver is not yet included in release, so that's why we use git version instead. I chose latest commit instead of commit with none driver. Description: Netavark is a rust based network stack for containers. It is being designed to work with Podman but is also applicable for other OCI container management applications. Signed-off-by: Oskari Rauta <oskari.rauta@gmail.com>