Since SkyWalking 8.8.0, the Dockerfiles are merged into the OAP repo and the Java agent repo respectively, this repo is archived and not maintained anymore.
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
- Java agent
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 to Docker Hub and available from the skywalking.docker.scarf.sh endpoint.
skywalking.docker.scarf.sh/apache/skywalking-base(Docker Hub)skywalking.docker.scarf.sh/apache/skywalking-ui(Docker Hub)skywalking.docker.scarf.sh/apache/skywalking-oap-server(Docker Hub)
Java agent images are available too.
skywalking.docker.scarf.sh/apache/skywalking-java-agent(Docker Hub)
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/v8.4.0.sh if the target version is 8.4.0
source <major_version>/v<version>.sh
makeAfter 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
makeVerifying 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.es7Pushing built images to docker hub repos:
make docker.pushThe 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.