[Discussion] TeamSpeak Server 3.10.x

[hunterpl]

Just to make sure.
Does your answer mean "The issue still exists and you already use hints_enabled=0" ?


We are not sure why you have such problems. Logs or recorded sessions from wireshark may help to see more.

Hello @dante696

Yes that was on our side fail with software raid and just strange backward settings networking same for optimization kernel sysctl.conf that's why it just stop after some minutes, anyway thank you for trying help. have a nice evening.

[hunterpl]

Just to make sure.
Does your answer mean "The issue still exists and you already use hints_enabled=0" ?


We are not sure why you have such problems. Logs or recorded sessions from wireshark may help to see more.

Hello @dante696

Yes that was on our side fail with software raid and just strange backward settings networking same for optimization kernel sysctl.conf that's why it just stop after some minutes, anyway thank you for trying help. have a nice evening.

[bluefire56]

Hi @dante696,

the Docker Image is still missing on Docker Hub . Could you please check this? Thank you!

[bluefire56]

Hi @dante696,

the Docker Image is still missing on Docker Hub . Could you please check this? Thank you!

[dante696]

We did requested changes and pushed a new version to Github.
Should be available within a day.

[dante696]

We did requested changes and pushed a new version to Github.
Should be available within a day.

[Hedius]

The docker image with the tag latest throws the following error atm:

| /opt/ts3server/entrypoint.sh: line 50: can't create /var/run/ts3server/ts3server.ini: Permission denied

Config: container runs in host namespace, volume mounted to /var/ts3server with permissions for user 9987.

The older images work without any problems. The given path is not part of the volume...

[Hedius]

The docker image with the tag latest throws the following error atm:

| /opt/ts3server/entrypoint.sh: line 50: can't create /var/run/ts3server/ts3server.ini: Permission denied

Config: container runs in host namespace, volume mounted to /var/ts3server with permissions for user 9987.

The older images work without any problems. The given path is not part of the volume...

[dante696]

Show us the full config or we can not see anything.

Please leave /var/run/ts3server/ alone or check your user permissions.

[dante696]

Show us the full config or we can not see anything.

Please leave /var/run/ts3server/ alone or check your user permissions.

[Hedius]

Show us the full config or we can not see anything.

Please leave /var/run/ts3server/ alone or check your user permissions.

I only quoted the error msg....

docker-compose:

version: '2.4'
services:
  ts3server_xyz:
    container_name: ts3server_xyz
    image: teamspeak:latest
    userns_mode: "host"
    network_mode: "host"
    restart: unless-stopped
    environment:
      TS3SERVER_LICENSE: accept
      TS3SERVER_QUERY_PROTOCOLS: "raw,ssh"

• docker-compose up

The container is not able to start.

Creating ts3server_xyz ... done
Attaching to ts3server_xyz
ts3server_xyz    | /opt/ts3server/entrypoint.sh: line 50: can't create /var/run/ts3server/ts3server.ini: Permission denied

I do not think that my config is special... Permissions should not be a problem, because it is 1:1 the default environment of the image without any modifications through volumes etc.

Docker version: Docker version 19.03.4, build 9013bf583a

[Hedius]

Show us the full config or we can not see anything.

Please leave /var/run/ts3server/ alone or check your user permissions.

I only quoted the error msg....

docker-compose:

version: '2.4'
services:
  ts3server_xyz:
    container_name: ts3server_xyz
    image: teamspeak:latest
    userns_mode: "host"
    network_mode: "host"
    restart: unless-stopped
    environment:
      TS3SERVER_LICENSE: accept
      TS3SERVER_QUERY_PROTOCOLS: "raw,ssh"

• docker-compose up

The container is not able to start.

Creating ts3server_xyz ... done
Attaching to ts3server_xyz
ts3server_xyz    | /opt/ts3server/entrypoint.sh: line 50: can't create /var/run/ts3server/ts3server.ini: Permission denied

I do not think that my config is special... Permissions should not be a problem, because it is 1:1 the default environment of the image without any modifications through volumes etc.

Docker version: Docker version 19.03.4, build 9013bf583a

[dante696]

We can not reproduce this with these settings.

What you could try is a docker-compose down and then docker-compose up again.
!!!! You loose your server data because you stored them in that docker and not on seperate mounted volume !!!!

Or you can try to run docker-compose up open a new folder.

[dante696]

We can not reproduce this with these settings.

What you could try is a docker-compose down and then docker-compose up again.
!!!! You loose your server data because you stored them in that docker and not on seperate mounted volume !!!!

Or you can try to run docker-compose up open a new folder.

[Hedius]

We can not reproduce this with these settings.

What you could try is a docker-compose down and then docker-compose up again.
!!!! You loose your server data because you stored them in that docker and not on seperate mounted volume !!!!

Or you can try to run docker-compose up open a new folder.

I store my data in volumes.
I just removed the volume section from the shown config, because it also happens with total clean containers. Recreating the container does not change anything.

The problem is that my docker daemon runs in a usernamespace.

my docker config is (etc/docker/daemon.json)

{
  "userns-remap": "default"
}

With this setting containers do not run as root on the host kernel by default. (So user id 0 is a really high user on the host) Isolation for security.

https://docs.docker.com/engine/security/userns-remap/

The compose file has the parameters:
userns_mode: host
network_mode: host

Network host just directly attaches the container to the host interfaces.
Userns_mode host is needed to bypass the mentioned isolation. The container runs then in the root namespace of the host system. (Same as in a default docker setup)

I am able to reproduce this issue on a Debian 9 and on a Debian 10 host.

A change in the docker image from version 3.9.1 to 3.10 made it incompatible with those settings....