-
-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
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
Tip for README Episode 7 #26
Labels
bug
Something isn't working
Comments
Weird! I wonder if they pulled 1.4.1... |
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
Not stale. |
This issue is no longer marked for closure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Jeff. Thanks for all the awesome work! I'm a big fan.
I ran into a problem wiht the Dockerfile that was generated but the oprator-sdk that I thought you may want to mention for anyone following along.
The generated dockerfile references
FROM quay.io/operator-framework/ansible-operator:v1.4.1
but as at today, there is only 1.4.0 available here https://quay.io/repository/operator-framework/ansible-operator?tab=tags
The upshot is the make step will fail at the docker-build step complaining that the image wasn't found. A quick manual modification to that line to change it to 1.4.0 fixes the problem.
Hope you're getting at least a little sleep with the new baby!
The text was updated successfully, but these errors were encountered: