Replies: 1 comment
-
Have done some more testing and dockerd seems to see envvars that are set via appended export statements on rc.conf with no other changes. exports, env_rc_allow, and /etc/env don't seem to have an effect on nerdctl/containerd that i can find just yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have tried the /etc/environment and /etc/rc.conf workaround but I still can't get either containerd or dockerd to leverage that config. Tried both explicit and "*" in the rc_env_allow and same result. Others noted that an export in rc.conf seemed to be respected, but that didn't work for me either. I have tried restarting RD, wsl --terminate rancher-desktop, wsl --shutdown, and power cycles of the machine and no change.
I have looked at the rc logs, but nothing is jumping out on why that model is not working. The files don't seem to be getting reset (like init.d scripts) so I feel like it "should" work, but I have yet to have it and more importantly detect why it's not working.
I know Proxy, DNS, etc. are booked to future releases which is great, but just looking to hardcode some things for the time being. Anyone have some tested workarounds or how to debug why the /etc/env+rc.conf isn't working?
Beta Was this translation helpful? Give feedback.
All reactions