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
cacheFrom configuration parameter is missing #484
Comments
ah, sorry for the inconvenience caused. We'll fix this. |
Thx for reporting |
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Nov 26, 2020
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Nov 26, 2020
12 tasks
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Nov 27, 2020
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Nov 27, 2020
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Dec 3, 2020
manusa
pushed a commit
that referenced
this issue
Dec 4, 2020
alexdeveng
pushed a commit
to alexdeveng/jkube
that referenced
this issue
Dec 24, 2020
…ration (eclipse-jkube#503) - Fix eclipse-jkube#484: CacheFrom parameter is missing in BuildConfiguration - Add @Singular annotation to cacheFrom in BuildConfiguration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Info
mvn -v
) :Migrated an existing working io.fabric8:fabric8-maven-plugin:4.4.1 configuration to org.eclipse.jkube:kubernetes-maven-plugin:1.0.2
Build configuration contains
mvn install results in this error:
The cacheFrom config element is described in jKube documentation at: https://www.eclipse.org/jkube/docs/kubernetes-maven-plugin#config-image
and was described in in fabric8-maven-plugin at: https://maven.fabric8.io/#config-image-build
However it seems to be absent from BuildConfiguration.java.
If it's a feature request, what is your use case :
It's a defect, not a feature request, but the use-case is, when building within a per-job docker-tooling-container environment, such as GitLab docker-in-docker, there is no local docker cache containing prior builds of the same image. Therefore it's necessary to "seed" the cache with the last-known good build from the main repository (a separate step in the gitlab pipeline) and then use "cacheFrom" to instruct fabric8/jkube/docker to use that image as a source of prior layers - this improves performance a great deal.
Sample Reproducer Project : [GitHub Clone URL]
The text was updated successfully, but these errors were encountered: