server.properties not being set about docker-minecraft-bedrock-server

[itzg]

@bingobob with a compose file you'll set

stdin_open: true
tty: true

on the service definition, described here. With that you can docker attach.

[creol]

@creol did you try restarting the server/container to pick up the change? Otherwise I would suggest the docker attach approve above and use the op command to change it at runtime.

Apparently I am my own worst enemy!
I created one MC container my kids were playing on while I have been working on a second container, but I accidentally forgot to remap the data folder. Both containers were working off the same /data/server.properties file, so of course nothing ever worked. Once I solved that I was able to make the default-player-permission-level=operator work.
Thank you!

[mattotone]

cat server.propertise show that settings are being set

[bingobob]

hi - i don't quite get this...

do edit server.properties file to set things up as i want them?

Or do i set the environment variables in my docker-compose and then that in turn writes to the server.properties file when the container is restarted/ recreated.

i've got it working but confused on config ?

Tahnks for any help?

[mattotone]

I never managed to get the full config to work, I set the environment variables in docker and it wrote them to the config files.
Cat server.properties shows them being written but the server appears to ignore them. maybe a bug in the game?

[itzg]

Since the Bedrock server is still beta this does seem to be one of the glitches due to that. Basically, it acts like most of the properties are only consulted on very first world creation even though the server will echo the modified properties on every startup. Gamemode was the property that most annoyed me.

If you make sure to include -i -t in the docker run, then you can always docker attach to the running server and use one of the commands to change the server behavior at any time.

[bingobob]

thanks for this, I'm running from a docker-compose file. Any tips to attach to the instance?

[creol]

How do I add opperators? I changed the permission.json but cant figure out how to apply the change. I tried permissions reload and it does not accept that command in bedrock.

[itzg]

@creol did you try restarting the server/container to pick up the change? Otherwise I would suggest the docker attach approve above and use the op command to change it at runtime.

[no-response]

This issue has been automatically closed because there has been no response after requesting feedback. Please feel free to re-open this issue if the scenario still exists and provide a comment with more information.

[bendinwire]

I have this exact same issue that @mattotone had above. Changes to the yml file alter the server.properties file and yet only one or two of them ever 'change'. Meaning I can change the MOTD, but the server name won't change.

My yml file:

version: "3"

services:
  mc:
    image: itzg/minecraft-server
    ports:
      - 25565:25565
    environment:
      EULA: "TRUE"
      OVERRIDE_SERVER_PROPERTIES: "true"
      MOTD: "Chaos Vibes Only"
      SERVER_NAME: "den"
      SEED: "-7783854906403730143"
    restart: unless-stopped
    volumes:
      - ./minecraft-data:/data

Produces server.properties file

$ cat server.properties | grep name
level-name=world
server-name=den

Bringing up the server with docker-compose it shows the Minecraft's servers name as Minecraft Server

I'm really stumped as to why it's not taking the setting (yet the MOTD) was updated for some reason). I thought that OVERRIDE_SERVER_PROPERTIES: "true" would fix it but it didn't.

Any suggestions?

[itzg]

@bendinwire so the server.properties entry

server-name=den

reflects the environment variable setting of SERVER_NAME: "den", right? If so, then this is an issue separate from the image startup scripts.

[bendinwire]

I agree with you that the yml seems to be producing the correct correlated file in server.properties, however when you view the server from a Minecraft client the name of the server still reads "Minecraft Server".

[itzg]

It sounds like an issue to report with Mojang.