SkyWalking Docker file archive for all official releases

Clone this repo:


  1. 9068c54 Fix my stupid typo by Zhenxu Ke · 8 days ago master
  2. f3550ba chore: upgrade the CLI version to 0.6.0, supporting Event report (#18) by Zhenxu Ke · 8 days ago
  3. 98c6aa0 Add Java agent Dockerfile and build / push script (#17) by Zhenxu Ke · 11 days ago
  4. a88cfda Update by 吴晟 Wu Sheng · 8 weeks ago
  5. d56272b Update by 吴晟 Wu Sheng · 8 weeks ago

Apache SkyWalking Docker Files

SkyWalking: an APM(application performance monitor) system, especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures.


This repository includes related files of following docker images:

  • OAP server
  • UI

Documents of each version are in v-x.y.z/oap and v-x.y.z/ui. Such as 8.1.0 OAP and 8.1.0 UI

The convenience images are published in docker hub.

How to build

When the version < 8.4.0, the release manifests are grouping by their major version number and full version number in archive.

From 8.4.0, issuing follows to build relevant docker images

# source 8/ if the target version is 8.4.0
source <major_version>/v<version>.sh


How to publish images

After a SkyWalking's Apache release, composing a new version environment setting script to <major_version> folder with the name like v<version>.sh

Building images as below:

source <major_version>/v<version>.sh

Verifying images:

# Booting up a compose of ES6, OAP server and UI
make compose.es6
# Booting up a compose of ES7, OAP server and UI
make compose.es7

Pushing built images to docker hub repos:

make docker.push

How to build images before 8.4.0

The manifests building images before 8.4.0 are archived into archive folder.

These “archived” images could not be built by any make target, being built manually instead. The approach is that navigating to the target based on the path grouped by SkyWalking release version number , then building specific images by docker build.


Apache 2.0 License.