-
|
So I'm having some problems migrating my world from a previous docker server to this one (The other docker image doesn't have mod support). No matter what I seem to do it just does not pull my existing world, and I was hoping someone could help point out if I have something wrong. So my host OS is Debian and it doesn't matter if I use this through docker compose or through Portainer stacks, same situation. I have downloaded my world files to my PC, created a new user in the docker group named "valheim" (PUID and PGID are 1001) and then run this docker compose (a few fields edited of course, the fields with xs) version: "3"
services:
valheim:
image: mbround18/valheim:latest
ports:
- 2456:2456/udp
- 2457:2457/udp
- 2458:2458/udp
environment:
PORT: 2456
NAME: "x"
WORLD: "x"
PASSWORD: "x"
TZ: "America/New_York"
PUBLIC: 0
AUTO_UPDATE: 1
AUTO_UPDATE_SCHEDULE: "0 1 * * *"
AUTO_BACKUP: 1
AUTO_BACKUP_SCHEDULE: "*/15 * * * *"
AUTO_BACKUP_REMOVE_OLD: 1
AUTO_BACKUP_DAYS_TO_LIVE: 3
AUTO_BACKUP_ON_UPDATE: 1
AUTO_BACKUP_ON_SHUTDOWN: 1
WEBHOOK_URL: "x"
UPDATE_ON_STARTUP: 1
PGID: 1001
PUID: 1001
volumes:
- /home/valheim/saves:/home/steam/.config/unity3d/IronGate/Valheim
- /home/valheim/server:/home/steam/valheim
- /home/valheim/backups:/home/steam/backupsI then check the start_server.sh to make sure it reflects the name, world and password (world name is absolutely correct, as a sanity check I have copy and pasted it's name), restart the docker container, log in (It takes the password I set, so I figure my settings should be correct) and the world it spawns me in is not the one from my old/existing server. The world files were uploaded via sftp with the valheim user, so I don't imagine permissions should be a problem. Am I missing something silly here? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 16 replies
-
|
When you log into the new world, does it create files on your system with a different world name or just overwrite your existing world? |
Beta Was this translation helpful? Give feedback.
-
|
I'm really not sure what the issue would be as long as Just to be sure there wasn't some weirdly specific case I ran a test server with the same world name and it created all the world files that I expected ❯ ls saves/worlds
SCATMANSWORLD.db SCATMANSWORLD.fwl SCATMANSWORLD.fwl.old |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I'm at a loss too, I'm half tempted to just dump the existing world at this point, sadly version: "3"
services:
valheim:
image: mbround18/valheim:latest
ports:
- 2456:2456/udp
- 2457:2457/udp
- 2458:2458/udp
environment:
PORT: 2456
NAME: "SCATMANSWORLD"
WORLD: "SCATMANSWORLD"
PASSWORD: "x"
TZ: "America/New_York"
PUBLIC: 0
AUTO_UPDATE: 1
AUTO_UPDATE_SCHEDULE: "0 1 * * *"
AUTO_BACKUP: 1
AUTO_BACKUP_SCHEDULE: "*/15 * * * *"
AUTO_BACKUP_REMOVE_OLD: 1
AUTO_BACKUP_DAYS_TO_LIVE: 3
AUTO_BACKUP_ON_UPDATE: 1
AUTO_BACKUP_ON_SHUTDOWN: 1
WEBHOOK_URL: "x"
UPDATE_ON_STARTUP: 1
PGID: 1002
PUID: 1002
volumes:
- /home/valdock/valheim/saves:/home/steam/.config/unity3d/IronGate/Valheim
- /home/valdock/valheim/server:/home/steam/valheimThis is the entirety of my compose file, with the password and webhook x'd out naturally. |
Beta Was this translation helpful? Give feedback.
-
|
That's very odd, nothing looks off :/ Have you tried renaming your existing files that you're trying to use to |
Beta Was this translation helpful? Give feedback.
-
|
You can also double-check the values in the docker environment with docker exec --user steam $CONTAINER_NAME envAnd make sure that |
Beta Was this translation helpful? Give feedback.
-
|
Can you create a copy of the old world called |
Beta Was this translation helpful? Give feedback.
-
|
Edit: I see you mentioned that now. Woops |
Beta Was this translation helpful? Give feedback.
-
|
Just checking in, I installed this last night and am running into the same issue. All my world save files are named the same as the docker-compose.yml The world files were transferred from a PC running Windows. It opens up the world with the name but nothing is saved from the original. It starts as a brand new world. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Hope if you find something it'll help future imports. We've made the most of it and rebuilt. Honestly, it's been great because we used knowledge from the previous world and helped to better shape this new one. :) This has been a great container and so happy that you have set it up, so thank you so much!! |
Beta Was this translation helpful? Give feedback.
-
|
alright @lyk4ndna i made a world, built a little tower using the steams Valheim Dedicated Server Tool and now started the docker container. Will update if i see my tower :P |
Beta Was this translation helpful? Give feedback.
-
|
Looks like my hypothesis was partially correct Part 1World engine broke: Take a look here as well: Second image you can see the scrap from my wood construct. Due to the nature of the world files being binary, you cannot try and convert them either.. Part 2Looks like i was being silly? I recopied the world from my local Valheim server into the Steps
|
Beta Was this translation helpful? Give feedback.
-
|
Ooo! Awesome thank you!! |
Beta Was this translation helpful? Give feedback.
-
Its a little janky to import worlds and does not always work. From some further testing, its easy for the world engine to mess it up pretty bad :< im hoping with hearth and home the world engine gets more stable. |
Beta Was this translation helpful? Give feedback.
-
|
@Aigis Did you end up starting a world from scratch? Edit: If not, I might found the solution |
Beta Was this translation helpful? Give feedback.
-
|
Can you share your solution? I may be having the same issue. Friend sent me their local world file from their Windows machine and I'm trying to start it up with the docker container on a Linux machine. However, it seems to always create a brand new world instead. Even more strange, it always creates the world with the same name and password as another freshly created World running on the same server in a different docker container. |
Beta Was this translation helpful? Give feedback.
-
|
Linux uses a case sensitive file system. For example, Pay attention to case @dossjj |
Beta Was this translation helpful? Give feedback.
Just checking in, I installed this last night and am running into the same issue. All my world save files are named the same as the docker-compose.yml
The world files were transferred from a PC running Windows. It opens up the world with the name but nothing is saved from the original. It starts as a brand new world.