We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
astro dev init
Describe the bug
You can recreate by brew install astro astro dev init vim Dockerfile
brew install astro
vim Dockerfile
You get the following: FROM quay.io/astronomer/astro-runtime:12.4.0
FROM quay.io/astronomer/astro-runtime:12.4.0
However when building we receive this error:
manifest for quay.io/astronomer/astro-runtime:12.4.0 not found: manifest unknown: manifest unknown
What CLI Version did you experience this bug?
1.30.0
This CLI bug is related to which Astronomer Platform?
What Operating System is the above CLI installed on?
Reproduced on Linux (can't recall distro) and Mac
🪜 Steps To Reproduce You can recreate by brew install astro astro dev init vim Dockerfile
The text was updated successfully, but these errors were encountered:
I think our astro deployment was upgraded to something, so checking out that out and trying to see what images are available.
Sorry, something went wrong.
I was able to remove the Dockerfile in our build pipeline and then recreate it with 12.3 image, and that works for now
No branches or pull requests
Describe the bug
You can recreate by
brew install astro
astro dev init
vim Dockerfile
You get the following:
FROM quay.io/astronomer/astro-runtime:12.4.0
However when building we receive this error:
What CLI Version did you experience this bug?
1.30.0
This CLI bug is related to which Astronomer Platform?
What Operating System is the above CLI installed on?
Reproduced on Linux (can't recall distro) and Mac
🪜 Steps To Reproduce
You can recreate by
brew install astro
astro dev init
vim Dockerfile
The text was updated successfully, but these errors were encountered: