Migrating World from backup file to server in docker container - backup world is overwritten

[konderla]

Hello,
I'm facing following issue - I want to migrate a my Minecraft (bedrock, v1.21.73) world I was playing on my Windows Minecraft client to docker server, to be able to play on it with others.
I've done following steps:

1. On Windows 11 I have exported the save world into .mcworld file.
2. I've created new docker volume for my new Minecraft container - mc_my_world (Linux Ubuntu 24.10, Minecraft Version: 1.21.73.01)
3. I've created new Minecraft container with /data poiting to mc_my_world
4. I've started container in order to initialize the world, make few steps around and build few blocks
5. I shut down the container
6. I open volume mc_my_wold and go to path: _data/worlds/Bedrock level/ and copy data from from by backup here. What I mean by that is that I extract from from .mcworld as this is .zip file.
7. I start the container back - and I have brand new world - not the one I have just copied.

My assumption was that this should be enough to replace the files in the "worlds" catalog with files from backup and it should work.
I have no idea how to solve this issue - all help is welcome.

Thanks - Michal

[itzg]

That procedure sounds right. At step 6, make sure it didn't unzip into a subdirectory of the world data there. In other words make sure it unzipped in a like for like structure.

[konderla]

Hello - thanks for the answer. Yes - I did make sure that file from the backup world are like for like in the folder structure. Today I'll make one more attempt and report results.
Question - is there any configuration entry in the docker container so that I could switch logs from basic to more developer like? My suspicion is that the starting docker in unable to ready correctly the newly uploaded/overwritten world. As a result is ignoring the map that is already in the folder and is starting new from scratch. This is the only logical explanation I can think about.

[itzg]

Question - is there any configuration entry in the docker container so that I could switch logs from basic to more developer like?

I don't know of any such option and therefore the image doesn't expose that.

My suspicion is that the starting docker in unable to ready correctly the newly uploaded/overwritten world. As a result is ignoring the map that is already in the folder and is starting new from scratch. This is the only logical explanation I can think about.

That seems virtually impossible since you would never be able to restart a server and have it retain the prior world data.

Perhaps you could share your container config, such as a compose file, to confirm the volume is setup correctly for persistence.

[konderla]

Hay - so, I have made one more attempt and it failed again. I'm attaching my configuration file - TXT as YAML is not supported as attachment format. Maybe this will help.
mc_michal_swiat.txt

[itzg]

I'll have to look later since I can't open that on my phone.

FYI just embed yaml content like

field: value

[konderla]

I have found the mistake. I was making an error while copying the backup files form original location to container. I was so focused on creating the container right and about configuration I have made mistake in the most obvious place.

@itzg - thank you for your help! And for the docker image - they are wonderful and provide a great platform for me and my family so we are able to play together! :-)

Problem solved. Scenario I've written in the first post is correct - you just have to look carefully while copying files. ;-)