-
Notifications
You must be signed in to change notification settings - Fork 330
natsbox doesn't work in openshift - can't cd to /root #858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
defect
Suspected defect such as a bug or regression
Comments
FYI my working config to deploy this via custom values is: natsBox:
enabled: true
container:
image:
tag: 0.14.2-nonroot
merge:
command:
- sh
- -ec
- |
work_dir="$(pwd)"
mkdir -p "$XDG_CONFIG_HOME/nats"
cd "$XDG_CONFIG_HOME/nats"
if ! [ -s context ]; then
ln -s /etc/nats-contexts context
fi
if ! [ -f context.txt ]; then
echo -n "default" > context.txt
fi
exec sh -ec "$0"
|
@jaredmcqueen would you try with nats-box 0.14.3-nonroot ? This MR should fix your issue : nats-io/nats-box#66 |
Should be fixed by #883 |
This is happening for me on v1.2.10, even with non-root. I am getting the following error: |
This config solves the above^ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version were you using?
natsio/nats-box:0.14.2-nonroot
What environment was the server running in?
RedHat OpenShift
Is this defect reproducible?
the helm chart currently starts the natsbox deployment using:
If I comment out that line it'll deploy. When I terminal into the container, my
$(pwd)
is/root
as expected but the kicker is that I can't change directory into that path. Odd because I'm in that path.If I go back a folder, then try to go back to
/root
I get a permission denied. Take a look at the following:Given the capability you are leveraging, describe your expectation?
deployments to openshift without modifying the helm chart or commenting out the
cd
Given the expectation, what is the defect you are observing?
permission denied
The text was updated successfully, but these errors were encountered: