add 8.6.0 (#20)

1 file changed
tree: 2e276cc1fa453db4c2688c2653dea1028afc4268
  1. .asf.yaml
  2. .gitignore
  3. 8/
  4. LICENSE
  5. Makefile
  6. README.md
  7. archive/
  8. base/
  9. compose/
  10. java-agent/
  11. oap-server/
  12. ui/
README.md

Apache SkyWalking Docker Files

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

Images

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 in docker hub.

Java agent images are available too.

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/v8.4.0.sh if the target version is 8.4.0
source <major_version>/v<version>.sh

make

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
make

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.

License

Apache 2.0 License.