[Discussion] TeamSpeak Server 3.10.x

[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....

[Hedius]

https://github.com/TeamSpeak-Systems...c0fd8f21c19f50

Probably the latest commit... Causes the problems. I will build the container myself this evening and try to find the problem...

[Hedius]

https://github.com/TeamSpeak-Systems...c0fd8f21c19f50

Probably the latest commit... Causes the problems. I will build the container myself this evening and try to find the problem...

[dante696]

Thank you for pointing out how you configured your system and why you use it that way. We did not have such situation on the radar.
As far as we know that is still an experimental feature but we will evaluate it and will eventually fix this for next server version.

As a workaround (and as you mentioned in your last post) building the container on your own should solve the issue.

[dante696]

Thank you for pointing out how you configured your system and why you use it that way. We did not have such situation on the radar.
As far as we know that is still an experimental feature but we will evaluate it and will eventually fix this for next server version.

As a workaround (and as you mentioned in your last post) building the container on your own should solve the issue.

[Midhun]

hi,

I need to know about the snapshot creation and deploy changes in new team-speak version 3.10.0. could you please provide the changes in team-speak command also, so that i can move to new version.

thank you!

[Midhun]

hi,

I need to know about the snapshot creation and deploy changes in new team-speak version 3.10.0. could you please provide the changes in team-speak command also, so that i can move to new version.

thank you!

[dante696]

Everything you need to know about the commands

help serversnapshotcreate
help serversnapshotdeploy

We overhauled the snapshots.

• They are now Base64 encoded. This makes them smaller and issues with UTF 8 characters should be gone.
• You now can encrypt your snapshot using a password. The password is AES encrypted and won't be shown in the server log in case logging was enabled.
• We added an optional parameter to move files from existing channels into the new one. But only if channel did exist before. This won't work with snapshots before 3.10.0.
• Older snapshots still can be applied, but you should create new ones after you did update.

[dante696]

Everything you need to know about the commands

help serversnapshotcreate
help serversnapshotdeploy

We overhauled the snapshots.

• They are now Base64 encoded. This makes them smaller and issues with UTF 8 characters should be gone.
• You now can encrypt your snapshot using a password. The password is AES encrypted and won't be shown in the server log in case logging was enabled.
• We added an optional parameter to move files from existing channels into the new one. But only if channel did exist before. This won't work with snapshots before 3.10.0.
• Older snapshots still can be applied, but you should create new ones after you did update.

[Midhun]

Everything you need to know about the commands

help serversnapshotcreate
help serversnapshotdeploy

Is this changes are optional?

[Midhun]

Everything you need to know about the commands

help serversnapshotcreate
help serversnapshotdeploy

Is this changes are optional?

[dante696]

Please read the change log. It says what is optional.

[dante696]

Please read the change log. It says what is optional.

[3rKaN_BRATTE]

Dante eine frage wann kommt ein Hotfix bzgl dem Bug denn ich bei Cobra Reported hab raus?

[3rKaN_BRATTE]

Dante eine frage wann kommt ein Hotfix bzgl dem Bug denn ich bei Cobra Reported hab raus?