space-engineers-dedicated-docker-linux: Error: No IP assigned.

Sometimes when I start the container, I see a few messages in the logs, and the server fails to start.

The messages are:

space-engineers-dedicated-docker-linux | 2021-10-02 23:03:44.920: CPU Info: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
space-engineers-dedicated-docker-linux | 2021-10-02 23:03:46.556: Bind IP : 0.0.0.0:27016
space-engineers-dedicated-docker-linux | dbus[71]: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file ../../../dbus/dbus-connection.c line 3544.
space-engineers-dedicated-docker-linux | This is normally a bug in some application using the D-Bus library.
space-engineers-dedicated-docker-linux | 
space-engineers-dedicated-docker-linux |   D-Bus not built with -rdynamic so unable to print a backtrace
space-engineers-dedicated-docker-linux | wine: Assertion failed at address 00007FA7050F37BB (thread 006c), starting debugger...
space-engineers-dedicated-docker-linux | 2021-10-02 23:03:59.363: Error: No IP assigned.

Just restarting the server doesn’t seem to help.

sudo docker-compose down && sudo service containerd restart && ./start seems to resolve it most of the time, however sometimes it doesn’t. Changing the container to/from host networking mode seems to resolve it sometimes also.

I’m not sure whats going on here, but I suspect it has to do with docker.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 17 (3 by maintainers)

Most upvoted comments

I am going to be forking the container to make my own take on this, I suspect some things may not be entirely up to date,

Already have some improved entry point scripts that help with permission issues and various setup tasks that are not defined in the Readme (fetching steamed for example)

On Mon, Nov 27, 2023, 11:55 PM xyadelaide @.***> wrote:

Has anyone found a way to fix this? Or is the only reliable way to delete the server and start over? I think that the best way to do this is to just use a Windows VM unfortunately. I can’t get this to work after trying a few fixes.

— Reply to this email directly, view it on GitHub https://github.com/mmmaxwwwell/space-engineers-dedicated-docker-linux/issues/25#issuecomment-1829282553, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPQOXWE5VZMWK7TSRF4AQ3YGWKF5AVCNFSM5FG5BSQKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBSHEZDQMRVGUZQ . You are receiving this because you commented.Message ID: <mmmaxwwwell/space-engineers-dedicated-docker-linux/issues/25/1829282553@ github.com>

Merith-TK on Nov 28, 2023

In this old source code of SE

            UInt32 ip = 0;
            UInt64 id = 0;

            int timeout = 100;
            while (ip == 0 && timeout > 0)
            {
                SteamSDK.SteamServerAPI.Instance.GameServer.RunCallbacks();

                Thread.Sleep(100);
                timeout--;

                ip = SteamSDK.SteamServerAPI.Instance.GameServer.GetPublicIP();
                id = SteamSDK.SteamServerAPI.Instance.GameServer.GetSteamID();
            }

            MySandboxGame.Services.SteamService.UserId = id;

            if (ip == 0)
            {
                MyLog.Default.WriteLineAndConsole("Error: No IP assigned.");
                return;
            }

            var ipAddress = IPAddressExtensions.FromIPv4NetworkOrder(ip);

It seems like Steam is handling the Public IP recognition, which is unnecesary when we define the ip in SpaceEngineersDedicated.cfg.

pyro000 on Apr 19, 2022

Yeah great work on keeping this going! I did end up disabling my SE container and running it under a VM for now. Were too many minor issues (No remote admin, this “No IP assigned” error, and then started getting “given key was not present in the directionary” errors).

With that last error, my world would not load, but I can load new worlds. It seems to happen when the world gets more complex as we play on it for a few weeks. (I clean a bunch of stuff up, removing entities, etc, and still no go).

The same exact world on a Wndows VM SE server works great. So yeah am back with running it on a Windows VM for now (sigh). I do like having my remote admin back though! Will definately keep an eye on this docker container though, great work! And your idea with the dynamically spawned instances on seperate containers sounds pretty durn cool!

whodat on Jan 1, 2022

When i’m developing using this container, switching between host and a few forwarded ports fixes it most times for a bit. Then it breaks again in a few mins, but I wasn’t setting the external IP in the config file.

Restarting containerd and docker help sometimes too, but every fix seems to encounter the same error after a few restarts, in my experience.

I expect you to run into the same problrm again soon. Please report back if you do, and if you run it for a few days and its fine, please report that back too!

mmmaxwwwell on Jan 1, 2022