Fix comment in config templates

This commit is contained in:
Jip-Hop 2024-06-23 18:33:20 +02:00
parent 2ce89c2945
commit 74e717a23b
5 changed files with 5 additions and 5 deletions

View File

@ -4,7 +4,7 @@ gpu_passthrough_nvidia=0
# Turning off seccomp filtering improves performance at the expense of security # Turning off seccomp filtering improves performance at the expense of security
seccomp=1 seccomp=1
# Use macvlan networking to provide an isolated network namespace, # Use bridge networking to provide an isolated network namespace,
# so docker can manage firewall rules # so docker can manage firewall rules
# Alternatively use --network-macvlan=eno1 instead of --network-bridge # Alternatively use --network-macvlan=eno1 instead of --network-bridge
# Ensure to change eno1/br1 to the interface name you want to use # Ensure to change eno1/br1 to the interface name you want to use

View File

@ -6,7 +6,7 @@ gpu_passthrough_nvidia=0
# TODO: don't disable seccomp but specify which syscalls should be allowed # TODO: don't disable seccomp but specify which syscalls should be allowed
seccomp=0 seccomp=0
# Use macvlan networking to provide an isolated network namespace, # Use bridge networking to provide an isolated network namespace,
# so incus can manage firewall rules # so incus can manage firewall rules
# Alternatively use --network-macvlan=eno1 instead of --network-bridge # Alternatively use --network-macvlan=eno1 instead of --network-bridge
# Ensure to change eno1/br1 to the interface name you want to use # Ensure to change eno1/br1 to the interface name you want to use

View File

@ -4,7 +4,7 @@ gpu_passthrough_nvidia=0
# Turning off seccomp filtering improves performance at the expense of security # Turning off seccomp filtering improves performance at the expense of security
seccomp=1 seccomp=1
# Use macvlan networking to provide an isolated network namespace, # Use bridge networking to provide an isolated network namespace,
# so kubernetes can manage firewall rules # so kubernetes can manage firewall rules
# Alternatively use --network-macvlan=eno1 instead of --network-bridge # Alternatively use --network-macvlan=eno1 instead of --network-bridge
# Ensure to change eno1/br1 to the interface name you want to use # Ensure to change eno1/br1 to the interface name you want to use

View File

@ -6,7 +6,7 @@ gpu_passthrough_nvidia=0
# TODO: don't disable seccomp but specify which syscalls should be allowed # TODO: don't disable seccomp but specify which syscalls should be allowed
seccomp=0 seccomp=0
# Use macvlan networking to provide an isolated network namespace, # Use bridge networking to provide an isolated network namespace,
# so lxd can manage firewall rules # so lxd can manage firewall rules
# Alternatively use --network-macvlan=eno1 instead of --network-bridge # Alternatively use --network-macvlan=eno1 instead of --network-bridge
# Ensure to change eno1/br1 to the interface name you want to use # Ensure to change eno1/br1 to the interface name you want to use

View File

@ -4,7 +4,7 @@ gpu_passthrough_nvidia=0
# Turning off seccomp filtering improves performance at the expense of security # Turning off seccomp filtering improves performance at the expense of security
seccomp=1 seccomp=1
# Use macvlan networking to provide an isolated network namespace, # Use bridge networking to provide an isolated network namespace,
# so podman can manage firewall rules # so podman can manage firewall rules
# Alternatively use --network-macvlan=eno1 instead of --network-bridge # Alternatively use --network-macvlan=eno1 instead of --network-bridge
# Ensure to change eno1/br1 to the interface name you want to use # Ensure to change eno1/br1 to the interface name you want to use