Update Failure with Minecraft - Cannot update Minecraft Bedrock to the newest version

[Robbie_Myers]

System Information

Field	Value
Operating System	Linux - Debian GNU/Linux 12 on x86_64
Product	AMP ‘Phobos’ v2.6.0.0 (Mainline)
Virtualization	Docker
Application	Minecraft
Module	MinecraftModule
Running in Container	Yes
Current State	Stopped

Problem Description

Issue

I have tried multiple times after updating AMP to 2.6 to install the newest Minecraft Bedrock update so I can connect to my worlds and it fails.

Reproduction Steps

• Changed to DEV servers
• Restart AMP
• Started physical Server

[Greelan]

Don’t use the legacy module

[Joshua_Heinaman]

Can you help me out here? Im on the development release for my instance and l’m unable to upgrade my bedrock server. What do you mean by don’t use the legacy module?

Im running AMP on Unraid in a docker container. I tried running the ampinstmgr upgradeall, but that doesn’t appear to upgrade the instance either?

Help?

[Greelan]

AMP on Unraid docker is unsupported.

Don’t run the Development build.

Bedrock was switched months ago to use the Generic Module rather than Minecraft Module

It appears as “Minecraft Bedrock” in the instance creation dropdown.

[vaiomusicman]

I had this same issue after updating,. My setup was AlmaLinux 9.4 running in Docker. I found that my server was using the Bedrock Legacy although I don’t remember that being a choice when I created the server.

My Solution was

1. Download a copy for the worlds/world directory from the legacy server.
2. Create a new instance and selecting bed “Minecraft Bedrock”
3. Starting new instance and allowing it to update and fully start
4. Stop new instance
5. Delete directory worlds/Bedrock Level
6. upload worlds/world and rename world to Bedrock level
7. Check file ownership, I had to change mine back to amp:amp
8. Change the server network port
9. Start server again

Hope this helps someone. The directory change from worlds/world to worlds/Bedrock Level is what held me up.