configmap file mount path results in command not found error #44815

pmcgrath · 2017-04-23T13:25:22Z

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): command not found configmap kubernetes

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

Kubernetes version (use kubectl version):
Client Version: v1.6.1 GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e"
Server Version: v1.6.0 GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37

Environment:

Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release): host is ubuntu 16.04
Kernel (e.g. uname -a): host is Linux dev1 4.4.0-72-generic Improved commit hook #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
Others: Running from within minikube version: v0.18.0

What happened:
When I try to create a deployment with a configmap file that is mounted into the same directory as the entry point , the container fails to start with the following error
"Error response from daemon: Container command '/app/app.sh' not found or does not exist."
The pod spec includes a configmap which is mounted into the same directory as the entrypoint

Seems the entry point script is lost after mounting the volume for the config map in the same directory
If I mount the configmap file into a sub directory all works as expected

What you expected to happen:
I expected the config map file to be created in the directory without effecting the existing directory content which in this case contains an entrypoint script

How to reproduce it (as minimally and precisely as possible):

Docker file - note the entry point

FROM busybox:latest

RUN        mkdir /app
COPY       app.sh /app

ENTRYPOINT ["/app/app.sh"]

Entry point script - infinite loop

#!/bin/sh
seq=1
while [[ true ]]; do
	echo "${seq} $(date) working"
	sleep .5s	
	let seq=$((seq + 1))
done

k8s configmap and deployment file

apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    product: k8s-demo
  name: demo
data:
  settings.json: |
    {
      "store": {
        "type": "InMemory",
    }

---
apiVersion: apps/v1beta1
kind: Deployment
metadata:
  labels:
    product: k8s-demo
  name: demo
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: demo
        product: k8s-demo
    spec:
      containers:
      - name: demo
        image: pmcgrath/shellloop:1
        imagePullPolicy: Always
        volumeMounts:
          - name: demo-config
            mountPath: /app
      volumes:
        - name: demo-config
          configMap:
            name: demo
            items:
              - key: settings.json
                path: settings.json

When I run the kubectl apply -d k8s.yaml and look at the pod I can see the following error

rpc error: code = 2 desc = failed to start container "f9e0112c80ebba568d4b508f99ffb053bf1ae5a4f095ce7f45bff5f38900b617": Error response from daemon: Container command '/app/app.sh' not found or does not exist.

Anything else we need to know:
If I change the mountPath for the volume to any other directory it works as expected

I did test this directly with docker on my host (17.03.0-ce) and it worked as expected

touch settings.json
docker container run -ti -v $(pwd)/settings.json:/app/settings.json pmcgrath/shellloop:1

The text was updated successfully, but these errors were encountered:

zhouhaibing089 · 2017-04-25T15:57:46Z

@pmcgrath

Checkout here.

it seems I understand your issue. I have the same question before, but there is an answer actually in your situation.

To brief your case, you have a configmap(settings.json: blahblah), and want to mount into a folder /app. Then below is what you need to know:

Once you mount a volume(no matter it is configmap or others), it overrides the mountPath, so in your case, the /app folder will only contain settings.json.
I know it is not what you expected, so you have to specify the mountPath: /app/settings.json, only that way, the original content in /app folders won't be affected.
well, when you do the second step, you remember that configmap is actually a list of key-value pairs, you only need one of the keys(though you actually have only one as well), so you need to tell the volume mounts to use a subpath from you configmap.

This is something that you will get eventually:

containers:
- volumeMounts:
  - name: demo-config
    mountPath: /app/settings.json
    subPath: settings.json
volumes:
- name: demo-config
  configMap:
    name: demo

pmcgrath · 2017-04-26T10:44:23Z

@zhouhaibing089
Thanks for the reply, works based on your suggestion, I appreciate the explanation

I am happy to close this issue
Pat

agilgur5 · 2017-11-02T00:55:36Z

For reference, the original mention of this solution seems to be here: #23748 (comment)

It looks like the documentation for this is missing, which makes this case fairly confusing/misleading, and the projection docs seem to make it more misleading as well -- not sure if it's missing because auto updates apparently don't work as per that issue

emwalker · 2017-12-28T03:53:36Z

The requirement for the file name to be specified both under mountPath and subPath is counterintuitive.

vishaltelangre · 2017-12-29T09:22:44Z

The solution provided by @zhouhaibing089 works but the content of the mounted file at subPath doesn't update if we edit it in the resembled ConfigMap.

leebenson · 2018-07-31T14:59:56Z

IMO, this isn't really solved. There should be an option to append each key rather than overwrite.

Something like:

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-conf
data:
  example1.conf: |
    server {
      server_name example1.com;
      # config here...
    }
  example2.conf: |
    server {
      server_name example2.com;
      # config here...
    }

So that...

- name: nginx-conf
  mountPath: /etc/nginx/conf.d
  append: true

... keeps the existing default.conf and any other artefacts of the Docker image, but augments with example*.conf

Repeating the same info in subPath is just icky.

mehemken · 2018-09-13T18:31:37Z

+1 on @leebenson 's append: true option.

val1715 · 2019-03-12T13:43:04Z

According to @leebenson answer: can anyone explain where from is coming append: true option ??

it does not work for me, i got:

error: error validating "hdfs/21-namenode-statefulset.yaml": error validating data: ValidationError(StatefulSet.spec.template.spec.containers[1].volumeMounts[1]): unknown field "append" in io.k8s.api.core.v1.VolumeMount; if you choose to ignore these errors, turn validation off with --validate=false

Also, it is not present in api docs for volume mount :
https://k8smeetup.github.io/docs/api-reference/v1.9/#volumemount-v1-core

Zvikan · 2019-03-18T10:26:52Z

According to @leebenson answer: can anyone explain where from is coming append: true option ??

it does not work for me, i got:
error: error validating "hdfs/21-namenode-statefulset.yaml": error validating data: ValidationError(StatefulSet.spec.template.spec.containers[1].volumeMounts[1]): unknown field "append" in io.k8s.api.core.v1.VolumeMount; if you choose to ignore these errors, turn validation off with --validate=false
Also, it is not present in api docs for volume mount :
https://k8smeetup.github.io/docs/api-reference/v1.9/#volumemount-v1-core

it doesn't exist, it's a suggestion. a good one for the use case.

fulopbede · 2019-04-24T11:13:03Z

I tried to use this method, but I got a Read-only file system error, when I applied the statefulset. Does anyone know how to fix that?
(I'm overwriting an existing file, that contains settings for elasticsearch, actual error message --> /usr/share/elasticsearch/bin/run.sh: line 28: ./config/elasticsearch.yml: Read-only file system)

pmcgrath closed this as completed Apr 26, 2017

zhouhaibing089 mentioned this issue May 3, 2017

Mount ConfigMap with Volumes as File #45000

Closed

asymmetric mentioned this issue Oct 5, 2017

Contents of service directory are hidden habitat-sh/habitat-operator#106

Closed

RoryQ mentioned this issue Nov 3, 2017

Allow setting subPath for Kubernetes VolumeMounts in CloudDriver spinnaker/spinnaker#2082

Closed

putcn mentioned this issue Nov 6, 2017

Run PaddleCloud on minikube. PaddlePaddle/PaddleCloud#463

Merged

deryadorian mentioned this issue Nov 20, 2017

configmap cannot be mounted as a file #56060

Closed

Nopik mentioned this issue Feb 12, 2018

RabbitMQ does not allow specifying config file helm/charts#3706

Closed

davidewatson mentioned this issue May 2, 2018

[CO-240] 2nd try to mount elasticsearch.yml only. Other configuration samsung-cnct/chart-elasticsearch#32

Merged

vincbe mentioned this issue May 21, 2018

ConfigMaps and Secrets mounted with subPath do not update when changed #50345

Closed

lentil1016 mentioned this issue Nov 21, 2018

如何去设置k8s 集群的时区呢 lentil1016/kubeadm-ha#17

Closed

alex-makrshakr mentioned this issue Dec 20, 2019

How to configure emqx-auth-username plugin correctly (RELEASE 3.1) emqx/emqx-auth-username#98

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

configmap file mount path results in command not found error #44815

configmap file mount path results in command not found error #44815

pmcgrath commented Apr 23, 2017

zhouhaibing089 commented Apr 25, 2017 •

edited

pmcgrath commented Apr 26, 2017

agilgur5 commented Nov 2, 2017

emwalker commented Dec 28, 2017

vishaltelangre commented Dec 29, 2017

leebenson commented Jul 31, 2018

mehemken commented Sep 13, 2018

val1715 commented Mar 12, 2019

Zvikan commented Mar 18, 2019

fulopbede commented Apr 24, 2019 •

edited

configmap file mount path results in command not found error #44815

configmap file mount path results in command not found error #44815

Comments

pmcgrath commented Apr 23, 2017

zhouhaibing089 commented Apr 25, 2017 • edited

pmcgrath commented Apr 26, 2017

agilgur5 commented Nov 2, 2017

emwalker commented Dec 28, 2017

vishaltelangre commented Dec 29, 2017

leebenson commented Jul 31, 2018

mehemken commented Sep 13, 2018

val1715 commented Mar 12, 2019

Zvikan commented Mar 18, 2019

fulopbede commented Apr 24, 2019 • edited

zhouhaibing089 commented Apr 25, 2017 •

edited

fulopbede commented Apr 24, 2019 •

edited