GitHub user assadali007 added a comment to the discussion: i am trying to do 
connect with docker this error come must be maping

this is yml file 
`version: '3.8'  # Add this as the very first line
x-airflow-common: &airflow-common
  environment:
    AIRFLOW__CORE__LOAD_EXAMPLES: "false"
    AIRFLOW__CORE__TEST_CONNECTION: "Enabled"
    AIRFLOW__DAG_PROCESSOR__REFRESH_INTERVAL: 60
    AIRFLOW__API_AUTH__JWT_SECRET: foo
    AIRFLOW__API__SECRET_KEY: bar
  volumes:
    - airflow-data-volume:/data

services:
  airflow-apiserver:
    <<: *airflow-common

  airflow-scheduler:
    <<: *airflow-common

  airflow-dag-processor:
    <<: *airflow-common

  airflow-worker:
    <<: *airflow-common

  airflow-triggerer:
    <<: *airflow-common

  airflow-init:
    <<: *airflow-common

  airflow-cli:
    <<: *airflow-common

  airflow-data:
#    image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:|version|}
    image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:latest}

    <<: *airflow-common
    entrypoint: /bin/bash
    command:
      - -c
      - |
        if [[ -z "${AIRFLOW_UID}" ]]; then
          echo
          echo -e "\033[1;33mWARNING!!!: AIRFLOW_UID not set!\e[0m"
          echo "If you are on Linux, you SHOULD follow the instructions below 
to set "
          echo "AIRFLOW_UID environment variable, otherwise files will be owned 
by root."
          echo "For other operating systems you can get rid of the warning with 
manually created .env file:"
          echo "    See: 
https://airflow.apache.org/docs/apache-airflow/stable/howto/docker-compose/index.html#setting-the-right-airflow-user";
          echo
        fi
        chown -R "${AIRFLOW_UID}:0" /data
        exec /entrypoint airflow version
    user: "0:0"

  events-api:
    build: ./docker/events-api
    image: manning-airflow/events-api
    ports:
      - "8081:8081"

volumes:
  airflow-data-volume:

`

GitHub link: 
https://github.com/apache/airflow/discussions/61534#discussioncomment-15719067

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to