-
Notifications
You must be signed in to change notification settings - Fork 46
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
Unable to enable loopback feature on IBM Cloud Openshift #595
Comments
Oh, I found the issue. I had to explicitly add this to the initContainer:
This is missing from the doc here -> https://github.com/logdna/logdna-agent-v2/blob/master/docs/KUBERNETES.md#enabling-file-offset-tracking-across-restarts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment: IBM Cloud Openshift cluster 4.13
Steps:
git clone [email protected]:logdna/logdna-agent-v2.git
cd logdna-agent-v2
git checkout 3.9.1
oc new-project logdna-agent
oc create serviceaccount logdna-agent
oc create secret generic logdna-agent-key --from-literal=logdna-agent-key=XXXXXX
oc adm policy add-scc-to-user privileged system:serviceaccount:logdna-agent:logdna-agent
k8s/agent-resources-openshift.yaml
with the following changes:volume-mount-permissions-fix
initContainer (using these steps)Problem:
The initContainer fails with:
Why would the
initContainer
running as root with theprivileged
SCC not be able to set permissions on/var/lib/logdna
?I even exec into the initContiner, and can see this:
Here is the final yaml I used:
The text was updated successfully, but these errors were encountered: