3.1.3
,3.1
(3.1/Dockerfile)3.1.3-onbuild
,3.1-onbuild
(3.1/onbuild/Dockerfile)3.2.1
,3.2
(3.2/Dockerfile)3.2.1-onbuild
,3.2-onbuild
(3.2/onbuild/Dockerfile)3.3.0-rc.1
,3.3.0
,3.3
(3.3/Dockerfile)3.3.0-rc.1-onbuild
,3.3.0-onbuild
,3.3-onbuild
(3.3/onbuild/Dockerfile)3.4.0
,3.4
,latest
(3.4/Dockerfile)3.4.0-onbuild
,3.4-onbuild
(3.4/onbuild/Dockerfile)
For more information about this image and its history, please see the relevant manifest file (library/haxe
). This image is updated via pull requests to the docker-library/official-images
GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the repos/haxe/tag-details.md
file in the docker-library/repo-info
GitHub repo.
Haxe is an open source toolkit based on a modern, high level, strictly typed programming language, a cross-compiler, a complete cross-platform standard library and ways to access each platform's native capabilities.
The Haxe compiler can output a number of source and binary files. As of Haxe 3.4.0-rc.1, the Haxe compiler can target JavaScript, Java, C#, C++, Python, PHP, Flash SWF, ActionScript 3, Lua, and Neko.
This image ships a minimal Haxe toolkit:
- the
haxe
compiler with its standard library - the
haxelib
library manager - the
neko
virtual machine
The most straightforward way to use this image is to use a Haxe container as both the build and runtime environment. In your Dockerfile
, writing something along the lines of the following will compile and run your project:
FROM haxe:3.4
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
# install dependencies
COPY *.hxml /usr/src/app/
RUN yes | haxelib install all
# compile the project
COPY . /usr/src/app
RUN haxe build.hxml
# run the output when the container starts
CMD ["neko", "Main.n"]
Then, build and run the Docker image:
$ docker build -t my-haxe-app .
$ docker run -it --rm --name my-running-app my-haxe-app
There are onbuild
variants that include multiple ONBUILD
triggers to perform all of the steps in the above Dockerfile, except there is no CMD
instruction for running the compilation output.
Rewriting the above Dockerfile with haxe:3.4-onbuild
, we will get:
FROM haxe:3.4-onbuild
# run the output when the container starts
CMD ["neko", "Main.n"]
The onbuild
variants assume the main compilation hxml file is named build.hxml
. To use another hxml file, set the BUILD_HXML
build argument during build:
$ docker build -t my-haxe-app --build-arg BUILD_HXML=compile.hxml .
View license information for the software contained in this image.
This image is officially supported on Docker version 1.13.1.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker
issue on the official-images
repository first.
You can also reach many of the official image maintainers via the #docker-library
IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
Documentation for this image is stored in the haxe/
directory of the docker-library/docs
GitHub repo. Be sure to familiarize yourself with the repository's README.md
file before attempting a pull request.