QEMU: Failed to create symbolic link .... No such directory or file #689

mikart143 · 2023-04-03T18:28:09Z

mikart143
Apr 3, 2023

Hi!
Great work!
I am having small trouble with running this on Oracle Ampere Free server.
My setup is based on docker compose and QEMU with emulators from: https://hub.docker.com/r/tonistiigi/binfmt
When I start server I receive error:

ln: failed to create symbolic link '/home/steam/.steam/root': No such file or directory
ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory

My docker-compose.yaml

version: "3"
services:
  valheim:
    privileged: true
    image: mbround18/valheim:latest
    platform: linux/amd64

    stop_signal: SIGINT
    ports:
      - "2456:2456/udp"
      - "2457:2457/udp"
      - "2458:2458/udp"
    environment:
      PORT: 2456
      NAME: "XXXXX"
      WORLD: "Dedicated"
      PASSWORD: "XXXXX"
      TZ: "Europe/Warsaw"
      PUBLIC: 0
      ENABLE_CROSSPLAY: 1
      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
      UPDATE_ON_STARTUP: 1
    volumes:
      - ./valheim/saves:/home/steam/.config/unity3d/IronGate/Valheim
      - ./valheim/server:/home/steam/valheim
      - ./valheim/backups:/home/steam/backups

Full log:

[Valheim][root] : Navigating to steam home...
[Valheim][root] : Launching as steam...
[Valheim][steam]: ###########################################################################
[Valheim][steam]: Valheim Server - Sun Apr  2 07:38:00 PM Europe 2023
[Valheim][steam]: STEAM_UID 1000 - STEAM_GUID 1000
[Valheim][steam]: Installing Valheim via odin 1.5.3...
[Valheim][steam]: ###########################################################################
[Valheim][steam]: Variables loaded.....
[Valheim][steam]: Port: 2456
[Valheim][steam]: Name: Pierdolnik na ARM
[Valheim][steam]: World: Dedicated
[Valheim][steam]: Public: 0
[Valheim][steam]: With Crossplay: 1
[Valheim][steam]: Password: (REDACTED)
[Valheim][steam]: Running Install...
[ODIN][INFO]  - Installing 896660 to /home/steam/valheim
[ODIN][INFO]  - steamcmd found in path
ln: failed to create symbolic link '/home/steam/.steam/root': No such file or directory
ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory
[ODIN][ERROR] - Exited with http code: 1

mbround18 · 2023-04-03T21:47:24Z

mbround18
Apr 3, 2023
Maintainer

I looked into those symbolic links, those are a steamcmd issue, i can toss over a "hey this is an issue" to them. What architecture is your host? arm, x86_64, etc

6 replies

mbround18 Apr 5, 2023
Maintainer

I am unsure if that would be truly compatible? are you able to run other x86 applications? if you docker run into the container via bash are you able to run the game server independently using the shell scripts inside the server directory?

spannerman79 Apr 5, 2023

My host is Arm but I am running this docker image as x86_64 via emu option in docker.

No, its only ment for android based docker images for dev/testing. Not to run a full fledged server created specifically for x86_64. And this goes for Valheim server - let alone steamcmd (which AFAIK doesn't work on arm/aarch correctly) and add on top Odin as well.

This is like expecting MS to suddenly open source windows and finally admit Linux is the king lol. Not going to happen.

mikart143 Apr 5, 2023
Author

I disagree. Sometimes you need to run this under different conditions. I am not trying to make any money out of this. All I want is to play with my friends. Having red oracle server and running this as my server would be no cost solution. Also I was running many times different container before rosetta on docker on my M1 MacBook without any issues.

mbround18 Apr 6, 2023
Maintainer

While this may be true, theres two software layers here and I would like you to help me diagnose which end is failing. @mikart143 in the docker container try and run one of the shell scripts. If the server doesnt come online, then the issue is with Valheim and not this repo. if the server boots up no problem and you can connect to it no issue then the issue is with this repo and I can take a look at it.

Would you mind running the shell scripts and getting back to me if it runs?

spannerman79 Apr 6, 2023

I disagree.

You can disagree until the cows come home. The issue here is that Valheim, developed by Iron Gate does not run native on aarch/arm.

Sometimes you need to run this under different conditions.

This only applies to say when @mbround18 decided to add mod support, and running it under different config options (V+, BepinEx, BepinExFull just to name three).

I am not trying to make any money out of this.

What does this have to do with the price of fish? (colloquialism). This is just hot air and has no bearing on this issue tracker nor this docker image.

Also I was running many times different container before rosetta on docker on my M1 MacBook without any issues.

Ahh this is the real reason behind your views. Well Apple has both the hardware and software behind the M1 as proprietary. The legal shit hole that the QEMU devs would be in if they used that same software would make it so that QEMU wouldn't exist due to take downs and legal issues.

Just because it worked on the M1 doesn't mean it will work on other hardware and on other VM software. It just doesn't.

cmorick · 2023-04-10T07:43:41Z

cmorick
Apr 10, 2023

@mbround18

ln: failed to create symbolic link '/home/steam/.steam/root': No such file or directory
ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory

Valheim server won't launch on arm64, but one can run this container on arm64 (with QEMU emulating x86_64) and get these ln/link errors. In fact, they appear in the logs for me on the x86_64 arch too. However, I do not get them from running the steamcmd:ubuntu image standalone. Unsure what that means for their source.

@mikart143

These ln errors aren't what blocks the Valheim server from running on arm64. It seems like your goal is achievable. You can do it, or you can join me in loving our limitations and just paying for a cheap x86_64 VM. I started and gave up, but I hope you're smarter than I am and have already walked away from it.

My setup is based on docker compose and QEMU with emulators from: https://hub.docker.com/r/tonistiigi/binfmt

tonistiigi/binfmt is an installer for emulators that can be used while building a Docker container. When you run tonistiigi/binfmt as intended, it installs available emulators or a selected sub-set of emulators, including QEMU, to your local Docker Engine.

From there, we might try to Docker compose up, but QEMU won't work that way, because compose runs related images. And at this point, nowhere has emulation been added to our image, it's just been installed to Docker Engine. To run the Valheim server with QEMU in a container, you have to build a multi-platform Docker image yourself.

I am having small trouble with running this on Oracle Ampere Free server.

Makes sense. On all public clouds, arm64 compute is far cheaper than x86 -- ARM chips simply use less electricity. And emulating x86 on arm64 can be done, in fact, it has been done. But what @spannerman79 was/is getting at is: it's probably not worth it to you.

OCI even provides a guide to what they call "nested KVM virtualization". With this architecture for our Valheim server within this container, we have to create many layers of virtualization between our app and the bare metal: the container, VMs, hypervisors, etc. Our cloud provider itself is running a hypervisor on its physical server to offer a virtual machine, we're running a hypervisor on their virtual machine, an emulator on our hypervisor -- and a container on top of that emulator to boot. Things are starting to sound a little recursive.

Every layer will drain a little slice of the physical resources off of the stack until your Valheim server at the final layer is gasping for air. The only way we can avoid it is by exposing the virtualized resources, creating a direct channel for our app between the virtual and the real. But even that doesn't solve for all of the setup, configuration, and checklist items. From the outside, it's cheap and seems easy enough, but down the road we start to see a more serious effect of all the layers.

For every abstraction between the physical compute and our app, we must add a little bit more complexity, spend a little bit more time, and feel a little bit more confused when things break. Here I found the following applies: "You spent so much time wondering if you could, you never stopped to think if you should"

If you only have 24 hours in your day like I do, then my suggestion is to do yourself a favor and stop while you're ahead: just run the mbround18/valheim using docker compose on a cheap x86 VM. Better yet, self-host it at home. Use OCI/GCP Preemptible or AWS/Azure Spot instances, and don't worry about getting stopped too often, I've had them up for weeks at a time.

If this all sounds like nonsense, take it for a spin, try it out. It's definitely possible. But then see how much time you spend. And you might come back and join me in accepting, even loving, the limits as they are. Thank God for the limitations; I, for one, will choose more sleep over more simulation.

1 reply

spannerman79 Apr 10, 2023

If you only have 24 hours in your day like I do

I, need my sleep, so I have less then 24 hours to muck around with something like that lol

But what @spannerman79 was/is getting at is: it's probably not worth it to you.

I've been down that rabbit hole. At the end of the day I tell the ones that want to play a game (be it Valheim etc);

Oi!, cough up some dosh to pay for the VPS over at Linode/Digital Ocean. Otherwise one of you lot can host it yourself.

I usually find that within an hour they have all given me money in order to go ahead.

clempat · 2023-04-10T17:38:36Z

clempat
Apr 10, 2023

I am having the same messages. The only difference is I am running it on an amd64 node:

Kernel version: 6.2.8-060208
OS/Arch: linux/amd64

My logs:


[ODIN][INFO]  - steamcmd found in path
ln: failed to create symbolic link '/home/steam/.steam/root': No such file or directory
ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory
Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".

That being said my logs does not explicitly say exiting with 1.

But my server is not running.

2 replies

mbround18 Apr 10, 2023
Maintainer

@clempat on a healthy server I am getting this

i do consider this a non issue and more of an annoyance

https://github.com/search?q=repo%3Ambround18%2Fvalheim-docker++ln+&type=code

clempat Apr 10, 2023

Ok, cool, thanks, so my problem is somewhere else. I will create another discussion.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

QEMU: Failed to create symbolic link .... No such directory or file #689

{{title}}

Replies: 3 comments 9 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

QEMU: Failed to create symbolic link .... No such directory or file #689

mikart143 Apr 3, 2023

Replies: 3 comments · 9 replies

mbround18 Apr 3, 2023 Maintainer

mbround18 Apr 5, 2023 Maintainer

spannerman79 Apr 5, 2023

mikart143 Apr 5, 2023 Author

mbround18 Apr 6, 2023 Maintainer

spannerman79 Apr 6, 2023

cmorick Apr 10, 2023

spannerman79 Apr 10, 2023

clempat Apr 10, 2023

mbround18 Apr 10, 2023 Maintainer

clempat Apr 10, 2023

mikart143
Apr 3, 2023

Replies: 3 comments 9 replies

mbround18
Apr 3, 2023
Maintainer

mbround18 Apr 5, 2023
Maintainer

mikart143 Apr 5, 2023
Author

mbround18 Apr 6, 2023
Maintainer

cmorick
Apr 10, 2023

clempat
Apr 10, 2023

mbround18 Apr 10, 2023
Maintainer