Replies: 1 comment 4 replies
|
You can't mount folder as /opt/airflow, because then airflow Helm will not be able to mount "airflow.cfg" file as secret in your mounted secret as folder (this is what you are observing) |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
My values.txt`
Docker Image customizations
I rebuilt the airflow base image and use it to replace the current image but using the default image can still replay the scenario
What happened
I created a configMap
>> kubectl create secret generic web-cert-and-key --from-file=/Users/s.eromonsei/Downloads/server.key --from-file=/Users/s.eromonsei/Downloads/server.crt -n airflow-devI am trying to mount the configMap airflow webserver to the following path using vulomeMount=> /opt/airflow I add my configuration to extraVolumes and extraMount, With the hope to reference the ssl crt and key in the mount path to the .cfg file for as shown below
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/var/lib/kubelet/pods/0c8d61a1-2bcb-448e-abe9-124b5c35dd1c/volume-subpaths/config/wait-for-airflow-migrations/0" to rootfs at "/opt/airflow/airflow.cfg": mount /var/lib/kubelet/pods/0c8d61a1-2bcb-448e-abe9-124b5c35dd1c/volume-subpaths/config/wait-for-airflow-migrations/0:/opt/airflow/airflow.cfg (via /proc/self/fd/6), flags: 0x5001: not a directory: unknownWhat you think should happen instead
My expectation is the data point server.crt and server.key will be available in the point , I can then pass to the airflow.cfg file
How to reproduce
Anything else
N/A
Are you willing to submit PR?
Code of Conduct
All reactions