JReleaser Docker Images

jreleaser-slim

Docker Pulls jreleaser-slim

Wraps the JReleaser CLI with an Ubuntu based Docker image: jreleaser/jreleaser-slim.
This image may be used to run JReleaser without having a pre-installed Java runtime on your system.

Additional packaging options such as Snapcraft and Chocolatey are not available in this mode.

Every command exposed by JReleaser CLI can be invoked with this image.

You must mount the working directory at the /workspace volume, for example assuming the current directory is the starting point:

$ docker run -it --rm -v `(pwd)`:/workspace \
  jreleaser/jreleaser-slim:<tag> <command> [<args>]
The jreleaser command will be automatically executed inside /workspace.

You may also need to map environment variables to the container, such as JRELEASER_PROJECT_VERSION, JRELEASER_GITHUB_TOKEN, or others depending on your setup.

You can find the tag listing here.

jreleaser-alpine

Docker Pulls jreleaser-alpine

Wraps the JReleaser CLI with an Alpine based Docker image: jreleaser/jreleaser-alpine.
This image may be used to run JReleaser without having a pre-installed Java runtime on your system.

Additional packaging options such as Snapcraft and Chocolatey are not available in this mode.

Every command exposed by JReleaser CLI can be invoked with this image.

You must mount the working directory at the /workspace volume, for example assuming the current directory is the starting point:

$ docker run -it --rm -v `(pwd)`:/workspace \
  jreleaser/jreleaser-alpine:<tag> <command> [<args>]
The jreleaser command will be automatically executed inside /workspace.

You may also need to map environment variables to the container, such as JRELEASER_PROJECT_VERSION, JRELEASER_GITHUB_TOKEN, or others depending on your setup.

You can find the tag listing here.

jreleaser-ubi

Docker Pulls jreleaser-ubi

Wraps the JReleaser CLI with a Red Hat Universal Base Image: jreleaser/jreleaser-ubi.
This image may be used to run JReleaser without having a pre-installed Java runtime on your system.

Additional packaging options such as Snapcraft and Chocolatey are not available in this mode.

Every command exposed by JReleaser CLI can be invoked with this image.

You must mount the working directory at the /workspace volume, for example assuming the current directory is the starting point:

$ docker run -it --rm -v `(pwd)`:/workspace \
  jreleaser/jreleaser-ubi:<tag> <command> [<args>]
The jreleaser command will be automatically executed inside /workspace.

You may also need to map environment variables to the container, such as JRELEASER_PROJECT_VERSION, JRELEASER_GITHUB_TOKEN, or others depending on your setup.

You can find the tag listing here.