Replies: 2 comments
-
Kernel command line doesn't need any special escape rules iirc. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Have you tried quoting the value without escape characters?
Are you using any templating to create your installation media? If you have a template engine or process the files through bash there may be escaping required. It would also help to know what version of Talos you're using and if you're using a system with UEFI or legacy BIOS because GRUB and systemd-boot may treat these arguments differently (although I don't think they do). |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We would like to set a username and password in a proxy url that is passed as kernel command line argument. We tried to use a general bash approach to handle special characters like this:
talos.environment='http_proxy=\"http://user!@#$:pa:ss\[email protected]:8080\"'
This failed and the proxy was not enabled for the auth device flow procedure. What would be a safe way to handle this?
Beta Was this translation helpful? Give feedback.
All reactions