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
Running minidcos docker doctor results in an error message about the default version of sed on macOs Mojave which includes an URL to the Versioning, Support and API Stability page
That page includes instructions for modifying the installation script to change the sed behavior: $ sed \ -e 'H;1h;$!d;x' \ -e "s/sed '0,/sed '1,/" \ dcos_generate_config.sh > dcos_generate_config.sh.bak
When this command is executed, I see this error message: sed: RE error: illegal byte sequence
I was able to workaround this by setting the LANG=C environment variable when executing the script: LANG=C sed -e 'H;1h;$!d;x' -e "s/sed '0,/sed '1,/" dcos_generate_config.sh > dcos_generate_config.sh.bak
There may be something specific about my development environment that is causing sed to error this way, so I'm creating this issue so that other folks will have this workaround.
The text was updated successfully, but these errors were encountered:
Running
minidcos docker doctor
results in an error message about the default version ofsed
on macOs Mojave which includes an URL to the Versioning, Support and API Stability pageThat page includes instructions for modifying the installation script to change the
sed
behavior:$ sed \ -e 'H;1h;$!d;x' \ -e "s/sed '0,/sed '1,/" \ dcos_generate_config.sh > dcos_generate_config.sh.bak
When this command is executed, I see this error message:
sed: RE error: illegal byte sequence
I was able to workaround this by setting the
LANG=C
environment variable when executing the script:LANG=C sed -e 'H;1h;$!d;x' -e "s/sed '0,/sed '1,/" dcos_generate_config.sh > dcos_generate_config.sh.bak
There may be something specific about my development environment that is causing
sed
to error this way, so I'm creating this issue so that other folks will have this workaround.The text was updated successfully, but these errors were encountered: