You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/05/25 07:52:52 UTC
[GitHub] [airflow] wittfabian opened a new issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
wittfabian opened a new issue #9003:
URL: https://github.com/apache/airflow/issues/9003
**Apache Airflow version**: 1.10.10
**Environment**:
- **OS**: Windows 10 / Docker Desktop
**What happened**:
According to the documentation it should be possible to build the image with the following command:
```
docker build . \
--build-arg PYTHON_BASE_IMAGE="python:3.7-slim-buster" \
--build-arg PYTHON_MAJOR_MINOR_VERSION=3.7 \
--build-arg AIRFLOW_INSTALL_SOURCES="apache-airflow" \
--build-arg AIRFLOW_INSTALL_VERSION="==1.10.10" \
--build-arg CONSTRAINT_REQUIREMENTS="https://raw.githubusercontent.com/apache/airflow/1.10.10/requirements/requirements-python3.7.txt" \
--build-arg ENTRYPOINT_FILE="https://raw.githubusercontent.com/apache/airflow/1.10.10/entrypoint.sh" \
--build-arg AIRFLOW_SOURCES_FROM="entrypoint.sh" \
--build-arg AIRFLOW_SOURCES_TO="/entrypoint"
```
**_Docker build failed with:_**
```
Step 32/90 : COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}
COPY failed: stat /var/lib/docker/tmp/docker-builder025357303/entrypoint.sh: no such file or directory
```
Before step 32 the required file "entrypoint.sh" is not provided/added.
**What you expected to happen**:
Successful build.
**How to reproduce it**:
Run the build command.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633527892
Will be there soon #8604 #8866 .. But if you want to make PR - feel free :)
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] wittfabian edited a comment on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
wittfabian edited a comment on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633463506
Oh, then I misunderstood.
I thought with `--build-arg ENTRYPOINT_FILE="https://raw.githubusercontent.com/apache/airflow/1.10.10/entrypoint.sh"` that would be possible.
`COPY scripts/include/clean-logs.sh /usr/local/bin/clean-airflow-logs` is also missing
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk closed issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
potiuk closed issue #9003:
URL: https://github.com/apache/airflow/issues/9003
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633453790
Yes. It's possible to build it from the sources. Apparently you only copied Dockerfile but not the entrypoint.sh which is needed as well. It's even written in the instructions [IMAGES.rst](https://github.com/apache/airflow/blob/master/IMAGES.rst) :
> This builds production image in version 3.6 with default extras from the local sources
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] wittfabian commented on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
wittfabian commented on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633466243
We need additional Airflow extras and Python dependencies for our production environment. The only possibility is to take over the github repo and build it in our own source control. Or is there a better solution?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] wittfabian commented on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
wittfabian commented on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633463506
Oh, then I misunderstood.
I thought with `--build-arg ENTRYPOINT_FILE="https://raw.githubusercontent.com/apache/airflow/1.10.10/entrypoint.sh"` that would be possible.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633453790
Yes. It's possible to build it from the sources. Apparently you only copied Dockerfile but not the entrypoint.sh which is needed as well. It's even written in the instructions [IMAGES.rst](https://github.com/apache/airflow/blob/master/IMAGES.rst) :
> This builds production image in version 3.6 with default extras from the local sources
You can build the image without entrypoint.sh present locally - but then it will need to be downloaded from the selected TAG in github. T
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #9003: "COPY ${AIRFLOW_SOURCES_FROM} ${AIRFLOW_SOURCES_TO}" failed on local build
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #9003:
URL: https://github.com/apache/airflow/issues/9003#issuecomment-633454722
You could also use
```
--build-arg AIRFLOW_SOURCES_FROM="Dockerfile" \
--build-arg AIRFLOW_SOURCES_TO="/dockerfile"
```
if you really want a standalone Dockerfile build. Feel free to make PR to update that in the documentation - I am happy to review it.
----------------------------------------------------------------
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:
users@infra.apache.org