eBot + Docker = <3

deStrO

Hello guys,

One member of the community made (@repz) worked hard on a Docker image for eBot. And I'm happy to announce that it's now working!

What's docker?
To make it simple, Docker is a kind of virtual host manager directly installed on your server with the ability to install & run a lot of software with simple commands on any operating system.
With a simple configuration file, you will have eBot running with latest features.

What are the requirements?
You need Docker & docker-compose installed on your server. This is quite common, no matter your operating system, it will works.
Find here the documentation to install docker: https://docs.docker.com/engine/installation/
And find here the documentation to install docker-compose: https://docs.docker.com/compose/install/
I won't provide any support on the Docker installation.

Once you installed everything, it's quite simple, copy & paste the content of that file https://github.com/jffz/docker-ebot/blob/master/docker-compose.yml in a empty directory (iike /home/csgo).
You will need to configure it a bit all values (EBOT_IP, etc...)

You have to know/understand just a bit that docker will "expose" the web port of the container. So if you are already running a web server, you will have to change the port binding.
https://docs.docker.com/compose/compose-file/#/ports

Once you configured everything, you just have to launch "docker-compose up -d" in the directory you pasted the docker-compose.yml file.

Here are the image used for eBot if you are a pro-docker:
https://hub.docker.com/r/hsfactory/ebotweb/
https://hub.docker.com/r/hsfactory/ebot/

Thanks again to @repz for his work!
Stay tuned for new updates 🙂

OlliC

Cool. Never used docker before, but i always wanted to check it out. I think now is the time :-)

repz

OlliC seems like it's time to do the jump 😉

Note that i'll do my best maintain those images up-to-date to latest updates from @deStrO.
It's already ready for the toornament integration update.

yahoo_1999

Is there actually any advantage in switching from regular install to the docker one? (Linux Noob here)

deStrO

yahoo_1999 If you have a working instance, don't switch 🙂

yahoo_1999

Ok, @deStrO Thanks!

OlliC

Just tried it out. Really fast and easy this docker thing :-)

I have one problem though. The Admin-Webinterface does not say "Ebot Online".

WebSocket online
Loading
Sound On (Turn Off)

All 3 docker container seem to run:

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                        NAMES
8e38d9032493        hsfactory/ebotweb   "/sbin/entrypoint.sh"    9 minutes ago       Up 9 minutes        0.0.0.0:80->80/tcp                                                           dockerebot_ebotweb_1
beb04cdde4f7        hsfactory/ebot      "/sbin/entrypoint.sh"    9 minutes ago       Up 9 minutes        0.0.0.0:12360-12361->12360-12361/tcp, 0.0.0.0:12360-12361->12360-12361/udp   dockerebot_ebot_1
1d44ecf756f1        mysql               "docker-entrypoint.sh"   9 minutes ago       Up 9 minutes        0.0.0.0:3306->3306/tcp                                                       dockerebot_mysql_1

Also there is a bootstrap.php process around:

$ ps ax|grep bootstrap
 6716 ?        Ssl    0:00 php /ebot/bootstrap.php

repz

OlliC

Looking at the pid of your bootstrap.php process, i guess this one is running on your host which maybe causing the ebot being offline.
The pid of the ebot in container is "1" on my side :

docker ps -a
CONTAINER ID        IMAGE                                        COMMAND                  CREATED             STATUS              PORTS                                                                        NAMES
f25a93661a73        hub.hsfactory.net/hsfactory/ebotweb:latest   "/sbin/entrypoint.sh"    18 hours ago        Up 18 hours         0.0.0.0:80->80/tcp                                                           ebot_ebotweb_1
869c1781e0d9        hub.hsfactory.net/hsfactory/ebot:latest      "/sbin/entrypoint.sh"    18 hours ago        Up 18 hours         0.0.0.0:12360-12361->12360-12361/tcp, 0.0.0.0:12360-12361->12360-12361/udp   ebot_ebot_1
97b48e4ee883        mysql                                        "docker-entrypoint.sh"   18 hours ago        Up 18 hours         0.0.0.0:3306->3306/tcp                                                       ebot_mysql_1
ebot:~# docker exec -it 869c1781e0d9 ps ax
  PID TTY      STAT   TIME COMMAND
    1 ?        Ssl   51:03 php /ebot/bootstrap.php
   22 ?        S      0:00 sh -c node /ebot/websocket_server.js 172.17.0.3 12360
   23 ?        Sl     0:07 node /ebot/websocket_server.js 172.17.0.3 12360
   35 ?        Rs+    0:00 ps ax

Try to kill this process and relaunch the compose file.

In your case:

# kill 6716
# cd </path/to/your/docker-compose.yml>
# docker-compose down; docker-compose up -d

OlliC

Fixed it now by doing docker-compose down and docker-compose up -d again. The second startup it worked.
Dont know what the problem was.

Inside the container the PID of the process was 1 here too. 6716 was the PID on the host system.
There is no other eBot installation as it is a newly installed virtualbox machine.

Thanks

carazzim0

nice,

I'm really looking forward to develop the ebotv4 container with you guys 🙂

OlliC

I was wondering how to start these containers on boot and also how to autorestart on crash.
You just have to add 'restart: always' to every container in the compose file. Maybe you could add that.

ebot:
  restart: always
  image: hsfactory/ebot
  links:
    - "mysql:mysql"
  ports:
    - "12360:12360"
    - "12361:12361"
    - "12360:12360/udp"
    - "12361:12361/udp"
  volumes:
    - /opt/docker/ebot/logs:/ebot/logs
    - /opt/docker/ebot/demos:/ebot/demos
  environment:
    EXTERNAL_IP: '192.168.2.118'
    MYSQL_HOST: 'mysql'
    MYSQL_PORT: '3306'
    MYSQL_DB: 'ebotv3'
    MYSQL_USER: 'ebotv3'
    MYSQL_PASS: 'ebotv3'
    LO3_METHOD: 'restart'
    KO3_METHOD: 'restart'
    DEMO_DOWNLOAD: 'true'
    REMIND_RECORD: 'false'
    DAMAGE_REPORT: 'true'
    DELAY_READY: 'false'

ebotweb:
  restart: always
  image: hsfactory/ebotweb
  links:
    - "mysql:mysql"
  ports:
    - "80:80"
  volumes:
    - /opt/docker/ebot/demos:/opt/demos
    - /opt/docker/ebot/logs:/opt/logs
  environment:
    EBOT_IP: '192.168.2.118'
    EBOT_PORT: '12360'
    EBOT_ADMIN_USER: 'admin'
    EBOT_ADMIN_PASS: 'admin'
    MYSQL_HOST: 'mysql'
    MYSQL_PORT: '3306'
    MYSQL_DB: 'ebotv3'
    MYSQL_USER: 'ebotv3'
    MYSQL_PASS: 'ebotv3'
    DEMO_DOWNLOAD: 'true'
    TOORNAMENT_ID: ''
    TOORNAMENT_SECRET: ''
    TOORNAMENT_API_KEY: ''
    TOORNAMENT_PLUGIN_KEY: ''

mysql:
  restart: always
  image: mysql
  ports:
    - "3306:3306"
  expose:
    - "3306"
  volumes:
    - /var/lib/mysql:/var/lib/mysql
  environment:
    - MYSQL_DATABASE=ebotv3
    - MYSQL_USER=ebotv3
    - MYSQL_PASSWORD=ebotv3
    - MYSQL_ROOT_PASSWORD=ebotv3

deStrO

Yes you can do that 🙂
Btw, I made an update that will solve your issue with the WebSocket connected but not eBot.

repz

Just updated with "restart: always", I also implemented the 'NODE_STARTUP_MEETHOD'.

OlliC

There seems to be a bug in hsfactory/ebot after the update. It does not start the bot and keeps trying to restart it.

What i did:

docker-compose down
docker-compose pull
docker-compose up -d

Also getting the new compose file.

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS                          PORTS                                                                        NAMES
db9de2cb6262        hsfactory/ebotweb   "/sbin/entrypoint.sh"    About a minute ago   Up About a minute               0.0.0.0:80->80/tcp                                                           dockerebot_ebotweb_1
114cc2585364        hsfactory/ebot      "/sbin/entrypoint.sh"    About a minute ago   Restarting (0) 37 seconds ago   0.0.0.0:12360-12361->12360-12361/tcp, 0.0.0.0:12360-12361->12360-12361/udp   dockerebot_ebot_1
49d23d26e299        mysql               "docker-entrypoint.sh"   About a minute ago   Up About a minute               0.0.0.0:3306->3306/tcp

repz

OlliC What's the output of

# docker logs 114cc2585364

OlliC

     |  _ \      | |
  ___| |_) | ___ | |_
 / _ \  _ < / _ \| __|
|  __/ |_) | (_) | |_
 \___|____/ \___/ \__|
 
PHP Compatibility Test
-----------------------------------------------------
| PHP 5.3.1 or newer    -> required  -> [ Yes ] 5.6.25
| Standard PHP Library  -> required  -> [ Yes ]
| MySQL                 -> required  -> [ Yes ]
| Sockets               -> required  -> [ Yes ]
| pthreads              -> required  -> [ Yes ]
-----------------------------------------------------
| Timezone is not set in php.ini. Please edit it and change/set "date.timezone" appropriately. Setting to default: 'UTC'
-----------------------------------------------------
| Registerung Shutdown function !
| Starting eBot Websocket-Server !
| Using 
| WebSocket server crashed
-----------------------------------------------------

repz

OlliC
I'll try to look tonight

Ducallion
172.17.0.4 is the docker internal network ip of your container.

The readme hasn't been updated, the correct url is : http://<ip>/admin.php

Btw, your image seems working. As the actual one is bugged, you should do not pull newest image until any news.

Ducallion

I have a small problem, as soon as I want to open up http://$hostip/ebot/admin.php - u:admin p:password,
with the right credentials, I get Error - Page not found!

What am I doing wrong?

PHP Compatibility Test

| PHP 5.3.1 or newer -> required -> [ Yes ] 5.6.25
| Standard PHP Library -> required -> [ Yes ]
| MySQL -> required -> [ Yes ]
| Sockets -> required -> [ Yes ]

| pthreads -> required -> [ Yes ]

| Timezone is not set in php.ini. Please edit it and change/set "date.timezone" appropriately. Setting to default: 'UTC'

| Registerung Shutdown function !
| Starting eBot Websocket-Server !

Notice: Undefined index: WORKSHOP in /ebot/src/eBot/Config/Config.php on line 63

| WebSocket has been started

2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG 2016-09-22 16:44:32 - LOG [eBot\Application\Application] eBot CS:GO version 3.2
[eBot\Application\Application] Loading config
[eBot\Config\Config] MySQL: mysql:3306 ebotv3:******@ebotv3
[eBot\Config\Config] Socket: 172.17.0.4:12360
[eBot\Config\Config] Advertising by Season:
[eBot\Config\Config] Maps:
[eBot\Config\Config] -> de_dust2_se
[eBot\Config\Config] -> de_nuke_se
[eBot\Config\Config] -> de_inferno_se
[eBot\Config\Config] -> de_mirage_ce
[eBot\Config\Config] -> de_train_se
[eBot\Config\Config] -> de_cache
[eBot\Config\Config] -> de_season
[eBot\Config\Config] -> de_dust2
[eBot\Config\Config] -> de_nuke
[eBot\Config\Config] -> de_inferno
[eBot\Config\Config] -> de_train
[eBot\Config\Config] -> de_mirage
[eBot\Config\Config] -> de_cbble
[eBot\Config\Config] -> de_overpass
[eBot\Application\Application] Registering MatchManager
[eBot\Manager\MatchManager] Creating MatchManager version 1.1
[eBot\Application\Application] Registering Messages
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\Attacked to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\BombDefusing to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\BombPlanting to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\ChangeMap to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\ChangeName to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\Connected to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\Disconnected to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\EnteredTheGame to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\GotTheBomb to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\JoinTeam to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\Kill to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\KillAssist to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\RoundEnd to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\RoundRestart to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\RoundScored to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\RemindRoundScored to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\RoundStart to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\RoundSpawn to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\Purchased to CSGO
[eBot\Manager\MessageManager] Adding message eBot\Message\CSGO\Say to CSGO

Where does this IP come from:
2016-09-22 16:44:32 - LOG [eBot\Config\Config] Socket: 172.17.0.4:12360

Ducallion

Thanx for the quick reply, I already tried, still Page not found....

Ducallion

By the way I realy like your work