• If you need help or want to discuss things, you now can also join us on our Discord Server!

Docker Image Installationsfehler

#1
Hey Community,

ich habe meinen kompletten Community Server auf Docker umgestellt. Ich habe dafür eine docker-compose.yml erstellt, in der sind ein TeamSpeak Server, eine MariaDB Instanz für den TeamSpeak Server, phpmyadmin und der Sinusbot als einzelne Services enthalten.

YAML:
version: '3.1'
services:
  teamspeak:
    image: teamspeak
    restart: always
    container_name: teamspeak
    ports:
      - 9987:9987/udp
      - 10022:10022/tcp
      - 30033:30033
    environment:
      TS3SERVER_DB_PLUGIN: ts3db_mariadb
      TS3SERVER_DB_SQLCREATEPATH: create_mariadb
      TS3SERVER_DB_HOST: tsdb
      TS3SERVER_DB_USER: root
      TS3SERVER_DB_PASSWORD: ***************************
      TS3SERVER_DB_NAME: teamspeak
      TS3SERVER_DB_WAITUNTILREADY: 30
      TS3SERVER_LICENSE: accept
      TS3SERVER_QUERY_PROTOCOLS: ssh
    volumes:
      - /opt/teamspeak3-data:/var/ts3server/
  tsdb:
    image: mariadb
    restart: always
    container_name: mariadb_ts
    ports:
      - 3306:3306
    environment:
      MYSQL_ROOT_PASSWORD: ******************
      MYSQL_DATABASE: teamspeak
    volumes:
      - /opt/tsdb-data:/var/lib/mysql
  phpmyadmin:
    image: phpmyadmin/phpmyadmin
    environment:
      MYSQL_ROOT_PASSWORD: ******************
    restart: always
    container_name: phpmyadmin
    ports:
      - 8080:80
    links:
      - tsdb:db
    volumes:
      - /sessions
  sinusbot:
    image: sinusbot/docker
    restart: always
    container_name: sinusbot
    ports:
      - 8087:8087
    volumes:
      - /opt/sinusbot-data/scripts:/opt/sinusbot/scripts
      - /opt/sinusbot-data/data:/opt/sinusbot/data
      - /opt/sinusbot-data/config:/opt/sinusbot/config
Es funktioniert alles ohne Probleme bis auf die Erstellung des Sinusbots. Bei diesem bekomme ich bei docker-compose up jedes mal einen Out of Memory Fehler. Es ist jedoch zu 100% genug RAM vorhanden. Es sind noch 1.2GB frei.

Server Konfiguration:
Distributor ID: Debian
Description: Debian GNU/Linux 9.5 (stretch)
Release: 9.5
Codename: stretch
Architecture: amd64

Its an VPS from OVH located in Limburg.
1 vCore (2% load average)
2 GB RAM
50 GB HDD


docker info : Hier

Installation Fehler:
Code:
Pulling sinusbot (sinusbot/docker:)...
latest: Pulling from sinusbot/docker
be8881be8156: Already exists
83f3f31a12e1: Pull complete
d7ce8cdffbf1: Pull complete
fddde7894119: Pull complete
26e48d383b40: Pull complete
fe0a3e5c582d: Pull complete
f2e142cbffd2: Pull complete
2383d722f1a6: Pull complete
86bbdd90a63e: Pull complete
7e45c0129b50: Pull complete
Digest: sha256:019d3cad0efcdf578bbab6302e9dd1f9f7f7ad41d846cd07836dbf8315e8b327
Status: Downloaded newer image for sinusbot/docker:latest
Creating sinusbot ... done
Attaching to sinusbot
sinusbot      | Copied original scripts to the volume
sinusbot      | Updating youtube-dl...
sinusbot      | Updating to version 2018.09.10 ...
sinusbot      | Updated youtube-dl. Restart youtube-dl to use the new version.
sinusbot      | youtube-dl updated
sinusbot      | Starting SinusBot...
sinusbot      | PID: 12
sinusbot      | fatal error: runtime: out of memory
sinusbot      |
sinusbot      | runtime stack:
sinusbot      | (0x10efe1b, 0x16)
sinusbot      |         :596 +0x95
sinusbot      | (0xc420300000, 0x5dd00000, 0x188f100, 0x18aa418)
sinusbot      |         :216 +0x1d0
sinusbot      | (0x188ee40, 0x5dd00000, 0x437f61)
sinusbot      |         :440 +0x374
sinusbot      | (0x188ee40, 0x2ee80, 0x0)
sinusbot      |         :774 +0x62
sinusbot      | (0x188ee40, 0x2ee80, 0x100)
sinusbot      |         :678 +0x44f
sinusbot      | (0x188ee40, 0x2ee80, 0x100000000, 0xc400000000)
sinusbot      |         :562 +0xe2
sinusbot      | ()
sinusbot      |         :627 +0x4b
sinusbot      | (0x7ffe87081ff0)
sinusbot      |         :343 +0xab
sinusbot      | (0x188ee40, 0x2ee80, 0x10100000000, 0x7ffe87082070)
sinusbot      |         :628 +0xa0
sinusbot      | (0x5dd00000, 0x7ffe87082001, 0x46b59e)
sinusbot      |         :807 +0x93
sinusbot      | ()
sinusbot      |         :702 +0x3e
sinusbot      | (0x1889d00)
sinusbot      |         :327 +0x79
sinusbot      | ()
sinusbot      |         :1132
sinusbot      |
sinusbot      | goroutine 1 [running]:
sinusbot      | ()
sinusbot      |         :281 fp=0xc420247358 sp=0xc420247350
sinusbot      | (0x5dd00000, 0xfc78e0, 0x553801, 0xc42006d180)
sinusbot      |         :703 +0x930 fp=0xc4202473f8 sp=0xc420247358
sinusbot      | (0xfc78e0, 0x5dd00000, 0x5dd00000, 0x6, 0xc420247601, 0x6)
sinusbot      |         :54 +0x7b fp=0xc420247448 sp=0xc4202473f8
sinusbot      | ()
sinusbot      |         :470 +0x4720 fp=0xc420247f88 sp=0xc420247448
sinusbot      | ()
sinusbot      |         :185 +0x20a fp=0xc420247fe0 sp=0xc420247f88
sinusbot      | ()
sinusbot      |         :2197 +0x1 fp=0xc420247fe8 sp=0xc420247fe0
sinusbot      |
sinusbot      | goroutine 17 [syscall, locked to thread]:
sinusbot      | ()
sinusbot      |         :2197 +0x1
sinusbot      |
sinusbot      | goroutine 5 [runnable]:
sinusbot      | ()
sinusbot      |         :20
sinusbot      | ()
sinusbot      |         :2197 +0x1
sinusbot      |
sinusbot      | goroutine 6 [runnable]:
sinusbot      | (0x11e2510, 0xc420013918, 0x10e1e99, 0x9, 0xc420022716, 0x3)
sinusbot      |         :271 +0x13a
sinusbot      | (0xc420013918, 0x10e1e99, 0x9, 0xc420022616, 0x3)
sinusbot      |         :277 +0x5e
sinusbot      | (0xfc0420, 0xc4200138c0, 0xc420022738, 0xffffffffffffff01, 0x9fd023, 0x6)
sinusbot      |         :229 +0x2dd
sinusbot      | (0xfc0420, 0xc4200138c0, 0xc420022738)
sinusbot      |         :113 +0x4d
sinusbot      | (0xc420065680, 0x6)
sinusbot      |         :156 +0xd3
sinusbot      | (0xc420065680, 0x11e2800)
sinusbot      |         :269 +0x1f2
sinusbot      | (0xc420065680)
sinusbot      |         :231 +0x58
sinusbot      | ()
sinusbot      |         :2197 +0x1

Ich habe auch das Docker [email protected] ausprobiert. Bei diesem Image bekomme ich genau den selben Fehler. Die Installation hat jedoch ohne Docker auf dem selben System vorher ohne Probleme geklappt.

Ich hoffe es hat jemand eine Lösung für das Problem.

Dazugehörige Github Issue

~ lusu007
 
Last edited by a moderator: