Note: this is the "per-architecture" repository for the windows-amd64
builds of the hylang
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:
Paul Tagliamonte, Hy BDFL -
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow
(See "What's the difference between 'Shared' and 'Simple' tags?" in the FAQ.)
1.0a1-python3.9-windowsservercore-1809
,python3.9-windowsservercore-1809
,1.0a1-windowsservercore-1809
,windowsservercore-1809
1.0a1-python3.9-windowsservercore-ltsc2016
,python3.9-windowsservercore-ltsc2016
,1.0a1-windowsservercore-ltsc2016
,windowsservercore-ltsc2016
1.0a1-python3.8-windowsservercore-1809
,python3.8-windowsservercore-1809
1.0a1-python3.8-windowsservercore-ltsc2016
,python3.8-windowsservercore-ltsc2016
1.0a1-python3.10-rc-windowsservercore-1809
,python3.10-rc-windowsservercore-1809
1.0a1-python3.10-rc-windowsservercore-ltsc2016
,python3.10-rc-windowsservercore-ltsc2016
1.0a1-pypy3.7-windowsservercore-1809
,pypy3.7-windowsservercore-1809
,1.0a1-pypy-windowsservercore-1809
,pypy-windowsservercore-1809
1.0a1-python3.9
,python3.9
,1.0a1
,latest
:1.0a1-python3.8
,python3.8
:1.0a1-python3.10-rc
,python3.10-rc
:1.0a1-pypy3.7
,pypy3.7
,1.0a1-pypy
,pypy
:
-
Where to file issues:
https://github.com/hylang/hy/issues -
Supported architectures: (more info)
amd64
,arm32v5
,arm32v6
,arm32v7
,arm64v8
,i386
,mips64le
,ppc64le
,s390x
,windows-amd64
-
Published image artifact details:
repo-info repo'srepos/hylang/
directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images repo'slibrary/hylang
label
official-images repo'slibrary/hylang
file (history) -
Source of this description:
docs repo'shylang/
directory (history)
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.
FROM winamd64/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 winamd64/hylang:0.10 hy your-daemon-or-script.hy
The winamd64/hylang
images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on Windows Server Core (microsoft/windowsservercore
). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
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.