-
Notifications
You must be signed in to change notification settings - Fork 519
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
Assembly descriptor removed but still in documentation #497
Comments
Which descriptors element are you referring to? I'm not able to find it in assembly configuration docs. |
just above section : 5.2.6. Assembly I was hoping for a drop in replacement but I was using this feature in fabirc8 |
ah, I'm sorry. Looks like we missed it. This is not supported anymore since we refactored jkube-kit out of maven. Could you please elaborate what you're trying to package into your Docker image using this |
The only option right now is for you to inline the descriptor in the configuration |
My assembly is:
it says lineEnding and dependencySets are not supported |
For these more complex scenarios, I would recommend using the maven-resources-plugin or maven-assembly-plugin first to preprocess and then use the target directory as the fileSet source for JKube. Check out an example here: http://blog.marcnuri.com/quarkus-jkube-qute-markdown-different-sources (The So. you can keep your assembly.xml descriptor, but you'll need to configure it the maven-assembly-plugin and run the assembly prior to kubernetes-maven-plugin build task. |
thanks, that worked, though I couldnt get it working with a Dockerfile, the docker file is so minimal I've converted it to xml and embedded it in the pom. I'm not sure if I'm allowed to mix a dockerfile and an assembly/inline - it's probably my lack of understanding about the copy path and using the directory assembly |
Yes you should be able Take a look at this quickstart https://github.com/eclipse/jkube/tree/master/quickstarts/maven/docker-file-provided which showcases different possibilities to work with external Docker files. I think you're probably interested in this one: |
OK this works for me:
Note that the contextDir is common to both the path to the dockerfile and the assembly directory
If you don't have a name configured in the assembly then you get a null pointer in the plugin I feel this is now really off topic to the orignal request |
Yes, we still need to fix the documentation or point to a workaround. |
@msillence : Hi, Would it be possible for you to help us by contributing a PR to fix documentation and provide workaround? |
When I moved this config to my real project it failed with an OOM - it was recursively adding the entire target folder to the docker image build in the target folder - until it failed This is my current config that doesn't suffer from that problem - not sure why it was working on the smaller test project:
and docker file now reads:
I'll have a think about the PR assuming that my workaround is the right approach |
hmmm, I'm afraid if this could be a bug in our plugin itself. Would it be possible for you to share a demo project so that we can reproduce this OOM error? |
…entation Remove assembly `<descriptor>` field from documentation as it's no longer supported
…entation Remove assembly `<descriptor>` field from documentation as it's no longer supported
…entation Remove assembly `<descriptor>` field from documentation as it's no longer supported
Remove assembly `<descriptor>` field from documentation as it's no longer supported
Description
descriptor support has been removed from the plugin but is still documented at the end of section 5.2.5 https://www.eclipse.org/jkube/docs/kubernetes-maven-plugin
This commit removed support:
cd47542#diff-7fe446a69cdae536171e449f96f5705c613db53de41eb9cddf032229e6e05893
Info
mvn -v
) : 3.0.6try and build a docker image using example documentation and you get the error:
Unable to parse configuration of mojo org.eclipse.jkube:kubernetes-maven-plugin:1.0.2:build for parameter descriptors: Cannot find 'descriptors' in class org.eclipse.jkube.kit.common.AssemblyConfiguration
The text was updated successfully, but these errors were encountered: