Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃摝 Publish a container image for kcctl to DockerHub #33

Open
gunnarmorling opened this issue Aug 13, 2021 · 9 comments
Open

馃摝 Publish a container image for kcctl to DockerHub #33

gunnarmorling opened this issue Aug 13, 2021 · 9 comments

Comments

@gunnarmorling
Copy link
Collaborator

Hey @aalmiray, is this something JReleaser would help with as well?

@gunnarmorling gunnarmorling changed the title Publish a container image for kcctl to DockerGub 馃摝 Publish a container image for kcctl to DockerHub Aug 13, 2021
@aalmiray
Copy link
Contributor

Yup, JReleaser can make it happen

@aalmiray
Copy link
Contributor

@gunnarmorling we need the following information:

  • a username/password for publishing to DockerHub. Store the password as a GitHub secret, I suggest using KCCTL_DOCKER_PASSWORD.
  • a DockerHub repository. The computed default would be kcctl/kcctl but feel free to pick a different name.
  • pick the base image. I think executables generated with Graal as we have them today require glibc, in which case that rules out any Linux Alpine base image. We could go with scratch or an Ubuntu based image.

@aalmiray
Copy link
Contributor

Slight complication, the docker packager expects .zip or .jar files as inputs. We currently have .tar.gz for the Linux artifact. The quick workaround is to use the .zip produced by the build, making sure the zip file is not signed/released (which JReleaser 0.6.0 can do).

@gunnarmorling
Copy link
Collaborator Author

I'll try and register the kcctl/kcctl repo. Re the base image, the Quarkus build can produce an image itself (either based on RHEL UBI, or distroless).

@aalmiray
Copy link
Contributor

That's the thing, at the moment JReleaser creates a Dockerfile based on a template, then creates the image, then published to a registry of your choice. It does not accept publishing a container image that was built from the outside, yet.

@gunnarmorling
Copy link
Collaborator Author

Ok, I see. I suppose we still can use the existing Dockerfile, right? One other question: can we deploy to quay.io instead of DockerHub? It seems the latter requires a paid plan now for setting up new organizations :(

@aalmiray
Copy link
Contributor

aalmiray commented Aug 13, 2021

Yes, we can deploy to Quay as well. You could setup a personal account at DockerHub, that's what I did for JReleaser, I did not migrate that account to org.

@aalmiray
Copy link
Contributor

jreleaser/jreleaser#358 Prevents the use of the quay.io/quarkus/quarkus-distroless-image:1.0 image however registry.access.redhat.com/ubi8/ubi-minimal:8.4 may be used. These two images are the ones defined by the Quarkus templates.

@mdwajid095
Copy link

Hello All,

I'm using kcctl as container. Really a nice, well readable tool for kafka connect.
Github: https://github.com/mdwajid095/wowsome/tree/main/kcctl
DockerHub: https://hub.docker.com/r/mdwajid095/kcctl

I think, we should include the docker image part in this project here itself. So, that everyone can use it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants