Skip to content
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

Problem in kubernetes op-connect-deployment.yaml example #84

Open
renepupil opened this issue Jul 11, 2024 · 0 comments
Open

Problem in kubernetes op-connect-deployment.yaml example #84

renepupil opened this issue Jul 11, 2024 · 0 comments

Comments

@renepupil
Copy link

The k8 deployment example at path examples/kubernetes/op-connect-deployment.yaml, has chmod -f -R 600 /home/opuser/.op/config as part of the command in the initContainer, but this path is not mounted, hence it does not have any effect on subsequent containers:

initContainers:
  - name: sqlite-permissions
    image: alpine:3.12
    command:
      - "/bin/sh"
      - "-c"
    args:
      - "mkdir -p /home/opuser/.op/data && chown -R 999 /home/opuser && chmod -R 700 /home/opuser && chmod -f -R 600 /home/opuser/.op/config || :"
    volumeMounts:
      - mountPath: /home/opuser/.op/data
        name: shared-data

Only /home/opuser/.op/data is mounted, chmod -f -R 600 /home/opuser/.op/config will ONLY affect the init container.

Did you mean chmod -f -R 600 /home/opuser/.config ?

But then you had to mount the credentials volume as well at path /home/opuser/.config...

If not, can you clarify what the intention was behind chmod -f -R 600 /home/opuser/.op/config ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant