#2526 When `meltano install` was run outside of Docker, `meltano invoke` and `meltano elt` fail with `ExecutableNotFoundError` inside Docker Issue created by MeltyBot Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2572 Originally created by @DouweM on 2021-02-10 174336 --- As reported in Slack by Pankaj Saini. Error:

meltano.core.plugin_invoker.ExecutableNotFoundError: Executable 'airflow' could not be found. Orchestrator 'airflow' may not have been installed yet using `meltano install orchestrator airflow`, or the executable name may be incorrect.

Caused by:

FileNotFoundError: [Errno 2] No such file or directory: '/project/.meltano/orchestrators/airflow/venv/bin/airflow': '/project/.meltano/orchestrators/airflow/venv/bin/airflow'

Unlike the error suggests, the plugin's own executable actually does exist at the identified path (relative from the Docker container), but the

python

executable pointed at by plugin executable's hashbang doesn't, since it uses an absolute path that was determined when

meltano install

was run outside of the Docker container, which won't be valid inside the container's environment. The solution is to always run

meltano install

and `meltano invoke`/`meltano elt` in the same environment, but we should: • make the error message less confusing • document this explicitly in https://meltano.com/docs/containerization.html#docker-compose / https://gitlab.com/meltano/files-docker-compose meltano/meltano