-
Notifications
You must be signed in to change notification settings - Fork 344
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
Passing image destination to build #437
Comments
kameshsampath
added a commit
to kameshsampath/camel-k
that referenced
this issue
Feb 14, 2019
kameshsampath
pushed a commit
to kameshsampath/camel-k
that referenced
this issue
Feb 14, 2019
kameshsampath
pushed a commit
to kameshsampath/camel-k
that referenced
this issue
Feb 14, 2019
Fixed by #438 |
valdar
pushed a commit
to jboss-fuse/camel-k
that referenced
this issue
May 21, 2019
ipolyzos
pushed a commit
to ipolyzos/camel-k
that referenced
this issue
Jul 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
currently the build form source produces the
docker.io/apache/camel-k
image; when testing builds and to enable using developer builds locally it will be better customize the image destination to be passed to the build.e.g.
make imageDestination=quay.io/myrepo images
should result in image with namequay.io/myrepo/camel-k
being produced, if the parameter is not passed then it will default todocker.io/apache/camel-k
The text was updated successfully, but these errors were encountered: