You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was able to use debug and log.format options successfully,
but suddenly cni stops working.
Neither of the cmd or pwsh variables, full path with forward or backward slashes - none of this matters,
these fields are simply ignored for some reason.
Copy nat.exe to C:\ProgramData\buildkitd\bin [1],
as well as regular cni conf [2] [3],
instead of conflist (it used to work when run from the command line).
The text was updated successfully, but these errors were encountered:
fruzitent
changed the title
Different behaviour between command line arguments and config file
Inconsistent behaviour between command line arguments and config file
Mar 19, 2024
Issue
containerd-cni-binary-dir
andcontainerd-cni-config-path
do work,but
worker.oci.cniBinaryPath
andworker.oci.cniConfigPath
do not.Steps to reproduce
Get
nerdctl
to generate default configuration it wants[1],
and replace
"cniVersion": "1.0.0"
with0.3.0
because of?
[1]
[2].
Point
buildkitd
to use this via command line arguments.It works!
Put the same settings in config file
[1].
It was able to use
debug
andlog.format
options successfully,but suddenly cni stops working.
Neither of the cmd or pwsh variables, full path with forward or backward slashes - none of this matters,
these fields are simply ignored for some reason.
Copy
nat.exe
toC:\ProgramData\buildkitd\bin
[1],
as well as regular cni
conf
[2]
[3],
instead of
conflist
(it used to work when run from the command line).It works!
Version
The text was updated successfully, but these errors were encountered: