Breaking News: Grepper is joining You.com. Read the official announcement!

script in configmap and used in pod permission

DreamCoder answered on December 11, 2022 Popularity 2/10 Helpfulness 1/10

answer script in configmap and used in pod permission

related script in configmap and used in pod permission

script in configmap and used in pod permission

Comment

The Deployment
A volume is created from the ConfigMap with defaultMode: 0744, that’s what makes it executable. It’s then mounted to a /scripts dir but it could be mounted anywhere. The command: ["/scripts/wrapper.sh"] overrides the Docker image’s entrypoint and runs wrapper.sh instead.

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: ghost
  labels:
    role: blog
spec:
  replicas: 1
  template:
    metadata:
      labels:
        role: blog
    spec:
      containers:
      - name: ghost
        image: ghost:0.11-alpine
        command: ["/scripts/wrapper.sh"]
        ports:
        - name: ghost
          containerPort: 2368
          protocol: TCP
        volumeMounts:
        - name: wrapper
          mountPath: /scripts
      volumes:
      - name: wrapper
        configMap:
          name: wrapper
          defaultMode: 0744

Popularity 2/10 Helpfulness 1/10 Language whatever

Source: etoews.github.io

Tags: configmap script whatever

Link to this answer
Share Copy Link

Contributed on Dec 11 2022

DreamCoder

0 Answers Avg Quality 2/10

Closely Related Answers

script in configmap and used in pod permission

Comment

volumes:
  - name: casacm-script
    configMap:
      name: {{ include "oxauth.name" . }}-casacm-script 
      defaultMode: 0777

Popularity 2/10 Helpfulness 1/10 Language whatever

Source: stackoverflow.com

Tags: whatever configmap script

Link to this answer
Share Copy Link

Contributed on Dec 11 2022

DreamCoder

0 Answers Avg Quality 2/10

script in configmap and used in pod permission

Comment

However, if you run that, the hiya pod will fail to start. Somewhere in the kubectl describe output, you should see an error like this:

starting container process caused "exec: \"/usr/local/bin/hello\": permission denied": unknown

By default, ConfigMaps mount in as non-executable. That makes sense, given that they are normally used for things like configuration files, data files, etc. What we’re doing is a bit unusual, but we have some options.
The first option is to change the command on the hiya container from this:

      command:
        - /usr/local/bin/hello
to this:

      command:
        - /bin/sh
        - /usr/local/bin/hello
        
That passes the script to /bin/sh as an argument, skipping the part where Linux tries to figure out how to run the script via the #!/... shebang at the top.
Note: this also means that whatever you do put in the shebang is ignored. This script will always run under the Bourne shell, /bin/sh. The shebang is now a comment.

Another way to fix this, that lets us avoid committing to an executor in the command: section is to mount the ConfigMap in with a different defaultMode.
  volumes:
    - name: bins
      configMap:
        name: bins
        defaultMode: 0755

Popularity 1/10 Helpfulness 1/10 Language whatever

Source: www.starkandwayne.com

Tags: whatever configmap script

Link to this answer
Share Copy Link

Contributed on Dec 11 2022

DreamCoder

0 Answers Avg Quality 2/10

script in configmap and used in pod permission

Contents

More Related Answers

script in configmap and used in pod permission

Closely Related Answers

script in configmap and used in pod permission

script in configmap and used in pod permission

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.