potiuk commented on issue #8605: URL: https://github.com/apache/airflow/issues/8605#issuecomment-704811657
> In this link(https://hub.docker.com/r/apache/airflow/dockerfile), there is no production level dockerfile is there. Yesterday saw the production version. I see it there (even in incognito mode). Must have been a temporary glitch of DockerHub. > > 1. Whether we need to pass dockerfile with -f flag? I have tried above command and observed , it is looking for dockerfile. As mentioned in the docs above, if you want to customize the image you need to checkout airflow sources and run the docker command inside the Airfllow sources. As it is in case of most Dockerfiles, they need context ("." in the command) and some extra files (for example entrypoint scripts) that have to be available in this context, and the easiest way it is to checkout Airflow Sources in the right version and customize the image from there. You can find a nice description in here: https://airflow.readthedocs.io/en/latest/production-deployment.html - we moved the documentation to "docs" and it has not yet been released (but it will be in 1.10.13) - but you can use the "latest" version - it contains all detailed description of customizing vs. extending and even a nice table showing what are the differences - one point there is that you need to use Airflow sources to customize the image. > 2. If AIRFLOW_INSTALL_SOURCES=".", it points the installation from local sources(as per documentation). How it works? See above - you need to run in inside checked out sources of Airflow. > 3. When I use the above command with -f Dockerfile, during the build process, I am facing this exception while running the step COPY scripts/docker scripts/docker --> "COPY failed: stat /var/lib/docker/tmp/docker-builder125807076/scripts/docker: no such file or directory". Whether i have to clone the git repo and then have to use docker build command? Yes. That's the whole point - customisation only works if you have sources of Airflow checked out. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
