-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Feature Request - build to docker without docker binary #3571
Comments
Hi @dimovelev, thank you for the feature request! Here are some related discussions: #2130, #1997. |
@mpeddada1 i am not sure what the result of the discussion is - do you want to use docker-java library or not? Assuming that you do not want to use it, we will have a bit more work to do:
parsing the request / response with jackson should be fine (we have jackson already as dependency). configuration-wise we could try to auto-configure depending on OS and socket/named pipe availability or require explicit configuration. |
@dimovelev We try to avoid third-party dependencies as much as possible in Jib, so the native solution you described is preferable. To clarify, we would accept a pull request for enabling non-docker scenarios, but this isn't on the team's roadmap to implement. |
I ended up writing a small maven / gradle plugin and publishing it to maven central - https://github.com/dimovelev/load-to-docker . It does what I needed - perform HTTP POST via named pipe on windows and unix domain socket on linux. I wanted to integrate it into jib but it seemed like a lot more work and I do not mind doing this in two steps - storing tarball with jib and then using the other plugin to load to docker. If at some point you decide that you want to integrate such a feature you could use it as a kind of proof-of-concept. I will leave it up to you to decide whether you want to close this issue or not. |
Thanks! We'll leave the issue open, so others can comment with their requirements. |
@chanseokoh What do you think about taking on |
I'm interested in support for nerdctl in containerd mode when using Rancher Desktop. I wonder if there are any plans for support? Unfortunately I don't know enough about Rancher Desktop/nerdctl/containerd details to propose a concrete solution. |
@Kitanotori We have no current plans, but keeping this issue open to evaluate demand. #2130 with ability to plug in different docker communication mechanisms is likely the best architectural approach. We've said in the past that |
Hi, I will be taking care of this implementation. I would like to discuss the following approach
This option allows to ship jib with both supports. It also enables to add new dependency to the plugin in maven and gradle and add the custom implementation via SPI. I was also looking at the plugin framework but doesn't seem to resolve this part and adding support for it can be a big one. Looking forward to hear from you. |
@eddumelendez Does that library work without any Docker component in host or target? |
@eddumelendez great news! Isn't the current implementation cli? What is the difference between default and cli? In a default mode it would be great if the plugin could autodetect what can be used - maybe check if the socket client can be used (e.g. named pipe exists, unix socket exists) and as a fallback use the docker cli. It might be necessary to add one more optional argument e.g. called url to be able to help the plugin find the right pipe, socket, host-port to talk to. An alternative suggestion for the new client's name could be HttpDockerClient (and mode http). |
@eddumelendez Thank you very much! Your plan sounds good to me. Thank you for considering the dependencies as optional -- adding them as plugin dependencies is ideal.
|
@eddumelendez I would also propose to do multiple steps, where the first step is to make Jib's |
right, no docker installation is required. It talks directly to the daemon that it is configured.
yes, by
It makes sense to me. Thanks for the feedback! I just wanted to make it explicitly for the user instead of make it work under the hood with not much aware but given the parameters that are needed we can implement what was suggested.
yes
this sounds a great approach |
Can it talk directly to containerd/buildkitd so that it could work with Rancher Desktop in containerd mode (might require changes at containerd first, though; see here)? Would it be possible to combine effort with containerd/nerdctl and Rancher Desktop teams to make jib work fully with RD without any Docker component? |
@eddumelendez great work! |
Description of the issue:
The docker build requires docker CLI to load the image built by jib to the docker daemon. It would be great if you could remove this dependency by implementing a simple HTTP post of the tarball to a configurable target. Example with curl:
So far the communication flavours that I am aware of are:
Expected behavior:
Being able to build to docker without a docker binary installed.
The text was updated successfully, but these errors were encountered: