Can't pull latest update

[OldDirtyPossum]

I'm still learning about Docker and, well, a lot in general. I recently upgraded the hardware I was running my server on, and in that time Minecraft Bedrock updated to 1.18.20.25, but when I try to get the container it's pulling the previous version. I've been working on this since early yesterday evening and I'm not figuring out what to do. I was going to try and just manually update inside the container using samba and my Windows file explorer, but I don't have permission, and I'm working on learning how to set that up. I saw an older post from someone who had an issue, and they had VERSION=LATEST set up and that fixed their issue. I'm trying that now but having issues. I have pulled the image twice now, previously I used a Docker Compose script that someone had set up and it worked great, and recently when that didn't work for some reason on the newer server hardware I created a docker-compose.yml in Notepad++ and copied the file onto my Ubuntu server into a Minecraft Directory I set up and had Docker create it.

I have dreams of eventually getting many certifications to advance my career, right now I'm a fledgling noob just trying to figure out how to have Minecraft Bedrock on a server that automatically restarts so my friends and family can enjoy when I'm out of town and for some reason the server reboots. Sorry if I need more help than most.

[itzg]

No need to worry about your questions. If you could provide the docker-compose.yml you're trying and the container logs from startup then that will help a bunch. Actually, before doing that please add DEBUG: "true" to your compose's environment section. It's an undocumented option that outputs the shell commands being executed.

[OldDirtyPossum]

Immediately after typing this I went with the original script I ran before, and it suddenly worked correctly. Give me a moment and I'm going to share the docker-compose.yml I was trying, and then script that worked, in case it helps someone else :)

[OldDirtyPossum]

And, you responed super fast, thank you :)

[OldDirtyPossum]

Version: "3"

services: minecraft: image: itzg/minecraft-bedrock-server volumes: - minecraftdata:/data - /home/Minecraft/plugins:/plugins ports: - 19132:19132 environment: EULA: "TRUE" TYPE: OPS: "Rhett1089" ENABLE_WHITELIST: "TRUE" ENFORCE_WHITELIST: "TRUE" tty: true stdin_open: true restart: unless-stopped volumes: minecraftdata: external: true

The one that just worked was

docker run
-d
-it
-p 19132:19132/udp
--name mcb
-e EULA=TRUE
--restart=always
itzg/minecraft-bedrock-server

The issue I was apparently having with that was I needed to log in as Root apparently, which I didn't have to do the first time I did it.

[itzg]

I had my email open right then 😉

I think I see what might be happening, but to offer a solution let me ask:

• do you have existing world data you want to keep?
• would want to map the container's data volume to a directory on your host machine for easier access?

As for needing to be root, see if this procedure helps with that.

[OldDirtyPossum]

At some point, if I can pick your brain, I'm also trying to set up the Kaede backup container that you mention on the Github page, and was totally lost in the woods trying to figure it out.

I have an existing world, but it had multiple corruptions and suffered what we refer to as the Chunkening. My minecraft community unanimously voted to have a fresh start on the newer hardware, so we aren't worried about that world right now, but I intend to load it up as an option for anyone who still wants to go there. Probably going to host on my buddies server, his equiptment is newer and with more headroom. I'm using a Dell T3500 I think, i7 920 with 24 gigs of DDR3 Ram.

I would love easier access to the container's data

[itzg]

I just added an example compose file that uses a relative host directory for the /data volume. I highly recommend that approach since it's both convenient to customize your server content yet have the container startup manage the server download/updates and properties configuration.

With that approach I modified your compose file with a few adjustments:

• lowercase version
• removed /plugins mount since that only applies to java edition container
• changed port mapping to UDP
• you'll need to lookup the XUIDs and provide those in OPS. More information is in this section
• adjust named of variable to be WHITE_LIST

version: "3"

services:
  minecraft:
    image: itzg/minecraft-bedrock-server
    volumes:
      - ./data:/data
    ports:
      - 19132:19132/udp
    environment:
      EULA: "TRUE"
      OPS: "your xuid"
      WHITE_LIST: "TRUE"
    tty: true
    stdin_open: true
    restart: unless-stopped

As for the Kaede backup container, I have not actually worked with it myself. If you join this Discord server here

https://discord.gg/tfwMcTMJ

There's actually a discussion going on today about setting that up.