sky-walking Server Docker Images

• Sky-walking server docker images use docker and compose tech. Please make sure, you are familiar with these techs. Use docker-compose mode to run servers, just fits for QUICK VIEW only.
• docker-compose.yml will link all servers and components : sky-walking routing server, sky-walking storage server, sky-walking alarm server, sky-walking webui and all dependency services, such as zookeeper, redis, mysql.
• In order to work, you should follow these steps, and set some arguments with your env or needs.

(1) Config the docker-compose.xml

• docker-compose.xml is in the root directory of the project.
• (Optional) set e-mail config. This config will be used, when sky-walking find exceptions or slow trace in the runtime. If you don't change this, you will not receive any alarm e-mail. Even in that case, all trace functions stay cool.

   - WEBUI_DEPLOY_ADDRESS=192.168.1.104:8080
   - ALARM_MAIL_HOST=smtp.mail.com
   - MAIL_USER_NAME=skywalking
   - MAIL_PASSWORD=skywalking
   - MAIL_SENDER_MAIL=skywalking@mail.com

• WEBUI_DEPLOY_ADDRESS is the ip:port pair of skywalking-webui.
• ALARM_MAIL_HOST is the host of mail server.
• MAIL_USER_NAME, MAIL_PASSWORD, MAIL_SENDER_MAIL are infos about your e-mail acount, which send alarm mails.

(2) Run in the root directory

   > docker-compose pull
   > docker-compose up

(3) Config your agent

• Set your agent -Dservers arg to ip:23000.

(4) Query trace in skywalking-ui

• You can access the UI on http://ip:8080/skywalking

ip should target your current mechine.

---

As I said, use docker-compose running cluster is a quick way to have a view of sky-walking tracer. It fits for QUICK VIEW only. Some times, it causes a delay (maybe long) to query trace of UI.

BUT

If you are an expert of docker, mesos or kubernates, as I thought, you can run the whole sky-walking servers in cluster mode, in a mesos/kubernates, after you have an fully understand of my docker-compose.yml. If so, that will be suitable for product env.