Gradle: Support for dockerizing non-java tools #1452
Comments
|
I believe Jib is trying to infer a main class since you didn't specify an entrypoint. You can specify the entrypoint using |
|
Nope, that does not work, classes are still trying to found. |
|
Oh sorry, I made an incorrect assumption. Jib tasks depend on the That said, this isn't really an intended use-case for Jib, since it is specifically meant to be an image builder for Java applications. If you do end up with a more complicated non-java scenario, you could look into using jib-core to write a custom image building plugin. |
|
By the way, you could also use Jib Core in your buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'com.google.cloud.tools:jib-core:0.1.1'
}
}
import com.google.cloud.tools.jib.api.Jib
import com.google.cloud.tools.jib.api.Containerizer
import com.google.cloud.tools.jib.api.RegistryImage
import com.google.cloud.tools.jib.frontend.CredentialRetrieverFactory
import com.google.cloud.tools.jib.image.ImageReference
task('dojib') {
doLast {
def targetImage = '<custom-docker-registry>/rabbitmq:3.7.8'
Jib
.from('rabbitmq:3.7.8')
.addEnvironmentVariable('ENV_NAME', 'ENV_VALUE')
.containerize(
Containerizer.to(
RegistryImage
.named(targetImage)
.addCredentialRetriever(
CredentialRetrieverFactory
.forImage(ImageReference.parse(targetImage))
.dockerConfig())))
println 'done'
}
} |
|
Closing since this isn't an intended use-case for Jib, and there are workarounds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the issue:
Using Gradle to bundle all docker images used in a project, java application as well as toolings required for application.
When trying to use Jib to dockerize non-java tools (using Gradle) it fails with exception around missing classes as it does not exist.
Tools in this particular project is RabbitMQ and MariaDB, and the dockerizing is mainly using the official images with the addition of custom environment variables
Expected behavior:
Running jib on non-java tools should possible and not fail.
Steps to reproduce:
Environment:
Gradle
jib-maven-pluginConfiguration:jib-gradle-pluginConfiguration:jib { from { image = "rabbitmq:3.7.8" } to { image = "<custom-docker-registry>/rabbitmq:3.7.8" } container { environment = ['ENV_NAME':'ENV_VALUE'] } }Log output:
Additional Information:
jib version: 1.0.0
The text was updated successfully, but these errors were encountered: