s390x/groovy
Apache Groovy is a multi-faceted language for the Java platform.
100K+
Note: this is the "per-architecture" repository for the s390x
builds of the groovy
official image -- for more information, see "Architectures other than amd64?" in the official images documentation and "An image's source changed in Git, now what?" in the official images FAQ.
Maintained by:
the Apache Groovy project
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile
linksWhere to file issues:
https://github.com/groovy/docker-groovy/issues
Supported architectures: (more info)amd64
, arm32v7
, arm64v8
, ppc64le
, s390x
Published image artifact details:
repo-info repo's repos/groovy/
directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/groovy
label
official-images repo's library/groovy
file (history)
Source of this description:
docs repo's groovy/
directory (history)
Apache Groovy is a powerful, optionally typed and dynamic language, with static-typing and static compilation capabilities, for the Java platform aimed at improving developer productivity thanks to a concise, familiar and easy to learn syntax. It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain-Specific Language authoring, runtime and compile-time meta-programming and functional programming.
Note that if you are mounting a volume and the uid running Docker is not 1000
, you should run as user root
(-u root
).
docker run -it --rm groovy
docker run --rm -v "$PWD":/home/groovy/scripts -w /home/groovy/scripts s390x/groovy groovy <script> <script-args>
The local Grapes cache can be reused across containers by creating a volume and mounting it in /home/groovy/.groovy/grapes
.
docker volume create --name grapes-cache
docker run --rm -it -v grapes-cache:/home/groovy/.groovy/grapes s390x/groovy
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info
repository's groovy/
directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
docker pull s390x/groovy