haxe pulls statistics

Quick reference

• Maintained by: the Haxe Foundation • Where to get help: the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow

Supported tags and respective Dockerfile links

(See "What's the difference between 'Shared' and 'Simple' tags?" in the FAQ.)

Simple Tags

• 4.3.7-trixie, 4.3-trixie • 4.3.7-bookworm, 4.3-bookworm • 4.3.7-windowsservercore-ltsc2025, 4.3-windowsservercore-ltsc2025 • 4.3.7-windowsservercore-ltsc2022, 4.3-windowsservercore-ltsc2022 • 4.3.7-alpine3.24, 4.3-alpine3.24, 4.3.7-alpine, 4.3-alpine • 4.3.7-alpine3.23, 4.3-alpine3.23 • 4.3.7-alpine3.22, 4.3-alpine3.22 • 4.3.7-alpine3.21, 4.3-alpine3.21 • 5.0.0-preview.1-trixie, 5.0.0-trixie, 5.0-trixie • 5.0.0-preview.1-bookworm, 5.0.0-bookworm, 5.0-bookworm • 5.0.0-preview.1-windowsservercore-ltsc2025, 5.0.0-windowsservercore-ltsc2025, 5.0-windowsservercore-ltsc2025 • 5.0.0-preview.1-windowsservercore-ltsc2022, 5.0.0-windowsservercore-ltsc2022, 5.0-windowsservercore-ltsc2022 • 5.0.0-preview.1-alpine3.24, 5.0.0-preview.1-alpine, 5.0.0-alpine3.24, 5.0-alpine3.24, 5.0.0-alpine, 5.0-alpine • 5.0.0-preview.1-alpine3.23, 5.0.0-alpine3.23, 5.0-alpine3.23 • 5.0.0-preview.1-alpine3.22, 5.0.0-alpine3.22, 5.0-alpine3.22 • 5.0.0-preview.1-alpine3.21, 5.0.0-alpine3.21, 5.0-alpine3.21 • 4.2.5-bookworm, 4.2-bookworm • 4.2.5-windowsservercore-ltsc2025, 4.2-windowsservercore-ltsc2025 • 4.2.5-windowsservercore-ltsc2022, 4.2-windowsservercore-ltsc2022 • 4.1.5-windowsservercore-ltsc2025, 4.1-windowsservercore-ltsc2025 • 4.1.5-windowsservercore-ltsc2022, 4.1-windowsservercore-ltsc2022 • 4.0.5-windowsservercore-ltsc2025, 4.0-windowsservercore-ltsc2025 • 4.0.5-windowsservercore-ltsc2022, 4.0-windowsservercore-ltsc2022

Shared Tags

• 4.3.7, 4.3, latest: • 4.3.7-trixie • 4.3.7-windowsservercore-ltsc2025 • 4.3.7-windowsservercore-ltsc2022 • 4.3.7-windowsservercore, 4.3-windowsservercore: • 4.3.7-windowsservercore-ltsc2025 • 4.3.7-windowsservercore-ltsc2022 • 5.0.0-preview.1, 5.0.0, 5.0: • 5.0.0-preview.1-trixie • 5.0.0-preview.1-windowsservercore-ltsc2025 • 5.0.0-preview.1-windowsservercore-ltsc2022 • 5.0.0-preview.1-windowsservercore, 5.0.0-windowsservercore, 5.0-windowsservercore: • 5.0.0-preview.1-windowsservercore-ltsc2025 • 5.0.0-preview.1-windowsservercore-ltsc2022 • 4.2.5, 4.2: • 4.2.5-bookworm • 4.2.5-windowsservercore-ltsc2025 • 4.2.5-windowsservercore-ltsc2022 • 4.2.5-windowsservercore, 4.2-windowsservercore: • 4.2.5-windowsservercore-ltsc2025 • 4.2.5-windowsservercore-ltsc2022 • 4.1.5-windowsservercore, 4.1-windowsservercore, 4.1.5, 4.1: • 4.1.5-windowsservercore-ltsc2025 • 4.1.5-windowsservercore-ltsc2022 • 4.0.5-windowsservercore, 4.0-windowsservercore, 4.0.5, 4.0: • 4.0.5-windowsservercore-ltsc2025 • 4.0.5-windowsservercore-ltsc2022

Quick reference (cont.)

• Where to file issues: https://github.com/HaxeFoundation/docker-library-haxe/issues • Supported architectures: (more info) amd64, arm32v7, arm64v8, windows-amd64 • Published image artifact details: repo-info repo's repos/haxe/ directory (history) (image metadata, transfer size, etc) • Image updates: official-images repo's library/haxe label official-images repo's library/haxe file (history) • Source of this description: docs repo's haxe/ directory (history)

What is Haxe?

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.

About this image

This image ships a minimal Haxe toolkit:

• the haxe compiler with its standard library • the haxelib library manager • the neko virtual machine

How to use this image

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:

Then, build and run the Docker image:

Using the onbuild variants

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:

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:

Image Variants

The haxe images come in many flavors, each designed for a specific use case.

haxe:

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.

Some of these tags may have names like bookworm or trixie in them. These are the suite code names for releases of Debian and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.

haxe:-windowsservercore

This image is based on Windows Server Core (mcr.microsoft.com/windows/servercore). 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:

• Windows Containers Quick Start

haxe:-alpine

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.…

Description from the Docker Hub listing.