itzg / itzg/docker-minecraft-bedrock-server

Recommendation on how to handle importing a world.

Open
#261 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
1.9k
Forks
303
Avg merge
2h 26m
Merged PRs (30d)
2

Description

### Discussed in https://github.com/itzg/docker-minecraft-bedrock-server/discussions/260

Originally posted by **chaoscode** July 2, 2022
I am attempting to move off a VM to this docker image for my daughters mc servers. The issue I am running into is important her world levels into the docker and have it be priested. I was thinking about forking the docker but I wanted to use your image to stay up to date. priested volumes don't help because I can not tell the game where the worlds folder is located. What is the best way to handle this?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Discussion 260 and the container volume and world configuration described in this issue. Determine whether importing an existing world is supported by the current image; done means documenting a reproducible supported procedure or identifying the required change.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.