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
While debugging an issue I had with our custom CNI plugin I just found out that libcni forwards every env variable of the program calling CNI.
While I could manage the programs env this leads me to the question whether this feature is really a good idea. Shouldn't libcni invoke plugins only with known CNI env variables?
In my case it was an env LOG_TARGET=stdout which made our custom CNI plugin to output debugging info to stdout and thus break the json output.
The text was updated successfully, but these errors were encountered:
cni/pkg/invoke/args.go
Line 57 in d5c71ad
While debugging an issue I had with our custom CNI plugin I just found out that libcni forwards every env variable of the program calling CNI.
While I could manage the programs env this leads me to the question whether this feature is really a good idea. Shouldn't libcni invoke plugins only with known CNI env variables?
In my case it was an env
LOG_TARGET=stdout
which made our custom CNI plugin to output debugging info to stdout and thus break the json output.The text was updated successfully, but these errors were encountered: