You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.
All the user needs to do is run fly auth docker and then they get the creds for pushing. From there they just set the KO_DOCKER_REPO env variable to be the name of their project.
Users can push to registry.fly.io/<app-name>:sha and then use the deploy command as a second step, or they can do (What you already have) as flyctl launch --image=$(ko build ./cmd/app)
Let me know if you'd like more clarification, or for me to submit a PR
In the docs the below is stated:
ko/docs/deployment.md
Lines 27 to 33 in f37f2d1
This is not correct on the image needing to be public. You are able to use Fly.io's docker registry, and push by logging in with
fly auth docker
I guess it's out of scope for this document to include that, but I thought it's something worth raising.
If you have any idea how this could be better explained in the docs, let me know and I'll open a PR
The text was updated successfully, but these errors were encountered: