Open tdhopper opened 1 year ago
I'm behind a that corporate VPN, so that could be the issue. However, I can access https://pip.astronomer.io/simple/
and the other urls from my browser without issue.
In the past users behind a corporate VPN sometimes have to add the urls as "trusted hosts" in a docker_congif/pip.conf
file.
https://stackoverflow.com/questions/59287824/specifying-multiple-trusted-hosts-in-pip-conf
@tdhopper Did you find a fix?
no
I had a similar issue and solved it by doing the following:
astro dev start
with the parameter -i
and pass the name of your custom docker imageAnother option is to add pip.astronomer.io
as a trusted-host and pass it to the image:
[global]
extra-index-url =
trusted-host = pypi.org
pypi.python.org
pip.astronomer.io
FROM quay.io/astronomer/astro-runtime:10.5.0
COPY pip.conf /home/astro/.pip/pip.conf
Build a custom image as detailed above and use it with -i
in the astro dev start
command
@jtrells , i followed this and able to create a build when there are no requirement. But when i add say astronomer-cosmos into requirements, the docker build is failing due to No matching distribution found for astronomer-cosmos.
any suggestions? thank you
I encountered a similar issue and found that the suggestion by @jtrells resolved the problem for me. To provide some context, the Dockerfile I used is as follows:
FROM quay.io/astronomer/astro-runtime:11.6.0
COPY pip.conf /home/astro/.pip/pip.conf
USER root
COPY <company>.crt /usr/local/share/ca-certificates/<company>/
RUN update-ca-certificates
USER astro
The pip.conf
file contains the following content:
[global]
extra-index-url =
trusted-host =
pypi.org
pypi.python.org
pip.astronomer.io
After creating a custom Docker image using this Dockerfile, I ran it using Astro CLI:
docker build -t myimage:0.1 -f Dockerfile .
astro dev start --image-name myimage:0.1
However, during the execution, I encountered the following known issue, which is documented here:
➜ dagbag git:(main) ✗ astro dev start --image-name myimage:0.1
Env file ".env" found. Loading...
[+] Running 0/0
⠿ postgres Error 0.0s
Error: error building, (re)creating or starting project containers: Error response from daemon: Please run 'docker login'
The solution that worked for me was to pull the Postgres image using the following command:
docker pull postgres:12.6
I am have this same problem and none of the above solutions are working for me. I'm running on a Mac with a brew install astro
instance. The version is 1.29.0.
My dockerfile FROM
is: FROM quay.io/astronomer/astro-runtime:12.1.0
It looks like the docker build process thatastro dev start
uses isn't working properly. /usr/local/bin/install-python-dependencies
is being run before either the certificates are updated or the pip.conf
is loaded.
My astro dev start
docker logs:
`[internal] load build definition from Dockerfile
transferring 699/0 0.004
[internal] load metadata for quay.io/astronomer/astro-runtime:12.1.0
[internal] load .dockerignore
[internal] load build context
transferring 652772/0 0.021
[1/7] FROM quay.io/astronomer/astro-runtime:12.1.0@sha256:77d85a8b6cd3bdfbcb25cbdb6ffbdb4ac2c1bb390b5951b836451dbdefb6c325
[2/7] COPY packages.txt .
[3/7] RUN /usr/local/bin/install-system-packages
Please Prioritize this guyz 👍🏻
Describe the bug
I'm trying to run
astro dev start
on a Mac and get a certificate error.What CLI Version did you experience this bug?
Astro CLI Version: 1.14.1
This CLI bug is related to which Astronomer Platform?
What Operating System is the above CLI installed on?
MacOS 13.3.1
🪜 Steps To Reproduce
brew install astro && astro dev start