• 0.13.1, 0.13, 0, latest (Dockerfile)

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

• Where to file issues:
  https://github.com/hylang/hy/issues

• Maintained by:
  Paul Tagliamonte, Hy BDFL

• Supported architectures: (more info)
  amd64, arm32v5, arm32v7, arm64v8, i386, ppc64le, s390x

• Published image artifact details:
  repo-info repo's repos/hylang/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/hylang
  official-images repo's library/hylang file (history)

• Source of this description:
  docs repo's hylang/ directory (history)

• Supported Docker versions:
  the latest release (down to 1.6 on a best-effort basis)

Hy (a.k.a., Hylang) is a dialect of the Lisp programming language designed to interoperate with Python by translating expressions into Python's abstract syntax tree (AST). Similar to Clojure's mapping of s-expressions onto the JVM, Hy is meant to operate as a transparent Lisp front end to Python's abstract syntax. Hy also allows for Python libraries (including the standard library) to be imported and accessed alongside Hy code with a compilation step, converting the data structure of both into Python's AST.

wikipedia.org/wiki/Hy

FROM hylang:0.10
COPY . /usr/src/myapp
WORKDIR /usr/src/myapp
CMD [ "hy", "./your-daemon-or-script.hy" ]

You can then build and run the Docker image:

$ docker build -t my-hylang-app
$ docker run -it --rm --name my-running-app my-hylang-app

For many simple, single file projects, you may find it inconvenient to write a complete Dockerfile. In such cases, you can run a Hy script by using the Hy Docker image directly:

$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp hylang:0.10 hy your-daemon-or-script.hy

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 hylang/ 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.