Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
laneyweb
@laneyweb
Hi Geoff. It's been a while since I posted here for help. I hope you dont mind me doing so again.. I had not played my Bedrock server with my kids for a while but all was OK before I recently updated to 1.16.0 - Now when I move around the world, the chunks dont generate and I'm left with stone only. I see this is a known bug here: https://bugs.mojang.com/browse/BDS-6230 - I am not sure what to do or how to follow the fix now I'm using your docker setup. Are you able to help with how I can fix this please? Thank you!
Geoff Bourne
@itzg
@laneyweb did you happen to update the docker image itself before doing the bedrock server update? There was an issue fixed in the image startup script where it avoided that bug you linked
laneyweb
@laneyweb
Hi. I only updated the server version to Version 1.16.40.2 by restarting my docker container. I didnt rebuild the image. Should I redo the docker build?
Geoff Bourne
@itzg
To clarify terminology, you just need a docker pull itzg/minecraft-bedrock-server not a "build"
however, I'm worried the damage is already done to your world data files unless you saved a backup prior to the version change
laneyweb
@laneyweb
eeek, me, an old IT professional with a backup.. oops :) - Yes, forgive me, I'm still a noob on the docker side and run the containers from my Synology NAS. I'm using Portainer to manage the them. I'lll get to the CLI and do a pull and see what the damage is.
Geoff Bourne
@itzg
I'm right there with you. Been in IT for years and still sporadic about backups :)
laneyweb
@laneyweb
hmm, that didnt seem to work. I have issued docker pull itzg/minecraft-bedrock-server on the NAS, and it pulled the latest files down but when I restart the container, create a new test world, it still has the same issue where all the chunks are stone. Do we think it has affected the persistent files?
Geoff Bourne
@itzg
With a totally fresh data directory it shouldn't start off with corrupted chunks. It sounds like your new container is still referencing the previous data.
Colin Alworth
@niloc132
you said you restarted the container, but after pulling you need to re-create it
laneyweb
@laneyweb
Hi @niloc132 - Thanks for that. I think I'm the problem ;) - I thought I could create a new world by stopping the container, editing the server.properties file by changing the "level-name=" to a new name and it would create a new world. Is that incorrect? Do I need to do a docker run with a new --name etc?
each time I want a new world?
Colin Alworth
@niloc132
the path to the world is the important part iirc - you may want to be careful about sharing other config files too? changing the container name is not necessary or sufficient
do you have volume mapped for your /data directory? i usually just make a new directory when i make a new world, and start fresh with configs, jars etc there
Geoff Bourne
@itzg
Yeah, fresh data directory is the easiest way to stay sane. That's odd it didn't work though, since level-name in the server.properties corresponds to the directory name under /data/worlds
...oh, maybe some of the incorrect bedrock bits are sitting around around from 1.14. Definitely try with a totally fresh /data mount @laneyweb
...now that the existing container directory looks like it is 1.16, the fixed upgrade script won't know to move away the 1.14 bits
laneyweb
@laneyweb
OK, thanks so much for the help. I am struggling with how to change this, sorry. I have these settings in the container
Host/volume Path in container
ae1021664c2b335a22d74946267f21439ec61df358f81e11e58dcbc8f4e5984e /data
/volume2/docker/bedrock/data/ops.json /data/ops.json
/volume2/docker/bedrock/data/permissions.json /data/permissions.json
/volume2/docker/bedrock/data/server.properties /data/server.properties
/volume2/docker/bedrock/data/worlds /data/worlds
both the old and new share the same ae102... path. How do I change to a new? Must I specify that when I rebuild the container?
Geoff Bourne
@itzg
What command do you use to create your container?
but yes via the -v argument
laneyweb
@laneyweb
ah. I used the Synology GUI. I am happy to try from the console but have not done it that way yet.
Geoff Bourne
@itzg
ah, it should have an equivalent for that called something about volume mounts/attachments
but rather than mount all of those individually, just mount /data to a directory managed by Synology
(if I'm interpreting what you pasted correctly)
laneyweb
@laneyweb
yes, it does. May I upload a screen shot to show the mapping?
Geoff Bourne
@itzg
Sure but again avoid fine grained mounts like that. In fact, I thought docker would disallow a mounted path within a mounted path
laneyweb
@laneyweb
deleted the old container and added a new one and that has recreated a new data directory. All fixed now so it was that there was files remaining in the old data directory that were the issue. My /data folder is not mapped so it is still within the container. If I added a map for that too, would it store all the files from data in the mapped volume folder I specify? And then I suppose I can map to a new one as and when I need to?
Also, now it is fixed. I can indeed just edit the /data/server.properties file and change the level-name= to a new world name and I get a new world generated in my mapped worlds directory
thanks for the help guys, much appreciated.
Geoff Bourne
@itzg
It won't automatically copy over files between an unnamed volume (which is the default) and then a host directory mapping. So I'd recommend going ahead and recreating the container now with a mapped /data before kids get busy rebuilding things :)
laneyweb
@laneyweb
will do! so if I do that and when the container restarts and gets the latest Minecraft 1.16.whatever, will that updated version go to that mapped volume?
Geoff Bourne
@itzg
Yes but at least now with the latest image, startup scripts it will properly move aside files during an upgrade to avoid the corrupted chunks type issues
laneyweb
@laneyweb
OK perfect. Thank you again. I currently map 3 config files and the data/world directory. If I redo the container and map the /data folder, I suppose I no longer need the individual mappings?
Geoff Bourne
@itzg
Correct, with the one mapping you can simply modify the config files in the mapped directory
Göran Sander
@mountaindude
Hey guys, new to the forums. Been reading up a bit on the history - looking great!
I am struggling with RCON in mc server 1.16.4 (Java). Which seems to be latest at this point. Running it in a small k3s cluster.
The server comes up fine, but RCON doesn't start, for some reason. Got ENABLE_RCON=true, but the RCON server just never starts. Any ideas?
Göran Sander
@mountaindude
Hmm, looks like the issue went away when I started over with a new/empty data dir. Maybe something went wrong when the Docker image was upgraded.
Elvis Chen
@chene77
hi, I am new to minecraft but do have some linux skills. I am trying to set up a basic server for my children (and their friends) so they can maintain some social activities in a controlled environment. I setup a Minecraft server (java) using the docker-compose-simple.yml and verified that the white-list is false in server.properties (after installation), and yet when I tried to connect to my own server on within my home LAN, I get a message:
Failed to connect to server: Failed to verify username! Can anyone suggest that may be wrong since I am not using any whitelist?
Geoff Bourne
@itzg
@chene77 that sounds more like it failed to contact the Mojang authentication servers. Do the container logs show anything additional at that point? You could try disabling online mode:
https://github.com/itzg/docker-minecraft-server#online-mode
Elvis Chen
@chene77
you are absolutely right, thanks. Kids and their friends are happy now.
Tailslide
@Tailslide
I'm trying to setup a server to run a custom modpack I made with curseforge with modloader set to forge-36.1.16. It runs fine single player but I can't get the server to load the mods. I Tried TYPE=Forge and TYPE=Fabric and TYPE=CURSEFORGE but nothing seems to work. Curseforge won't start the server at all and the other ones say "Incomplete set of tags received from server". This is my first time using itzg/dockerfiles. Help ?
Tailslide
@Tailslide
Nevermind think I got it going.. some really strange stuff going on with permissions.. setting UID and gid didn't work I had to run without the data volume mounted then copy everything to my volume and manually set the permissions.
lcluarlp
@lcluarlp
Hi, I tried to setup a Paper sever, which worked fine when I just used the defaults. However the server ignored, when I tried to limit the number of players or the world size. I tried the same as below with a spigot server and it worked. I am a docker and mc newbie.
Here is the docker-compose file (I used docker-compose in order to prepare for several servers on my kids demand).
services:
mc-paper:
image: itzg/minecraft-server
ports:
  - 25565:25565
environment:
  TYPE: PAPER
  EULA: "true"
  SEED: 2021
  MAX_WORLD_SIZE: 10000
  MAX_PLAYERS: 10
tty: true
stdin_open: true
volumes:
  - /home/name/data/mc-paper:/data
restart: always
Geoff Bourne
@itzg
Try adding OVERRIDE_SERVER_PROPERTIES=true since it won’t modify those properties if it finds the file already exists
FYI chat has moved over to Discord at https://discord.gg/DXfKpjB
lcluarlp
@lcluarlp
very kind. thank you so much.
cburza
@cburza

I am having some issues getting backups to work with new Helm chart version 3.6.3. I keep getting the error time="2022-01-14T15:22:23Z" level=fatal msg="Failed to run sub-command" error="fork/exec /usr/bin/backup: operation not permitted". From the debugging I cannot seem to find an issue with the permissions. The backup script runs fine when I bypass /opt/entrypoint-demoter

I think it is because the container is not run as a privileged user and entrypoint-demoter cannot change the user. Any pointers on getting this to work with entrypoint-demoter?

cburza
@cburza

So the only way the backup runs is when I add the following to the backup container:

securityContext:
          runAsUser: 0

After this all works.