search

goofball222 / factorio

Factorio headless server Docker container
Apache License 2.0
47 stars 14 forks source link

Kernel too old error (Jelastic) #2

Closed JyeGuru closed 6 years ago

JyeGuru commented 6 years ago

I've always used various Factorio docker images on a Jelastic host (MassiveGrid) to easily create dedicated servers that are simple to use and configure for playing with friends. However, when I attempted to use this one today it gave me the below error (using experimental build):

2018-01-09T22:41:25.344 <docker-entrypoint> INFO - Script version 0.2.5
2018-01-09T22:41:25.366 <docker-entrypoint> INFO - Entrypoint running with UID 0 (root)
2018-01-09T22:41:25.374 <docker-entrypoint> INFO - UID/GID for factorio are unchanged: UID=999, GID=999
2018-01-09T22:41:25.381 <docker-entrypoint> INFO - Using existing RCON.pwd found in /opt/factorio/config
2018-01-09T22:41:25.395 <docker-entrypoint> INFO - RCON password is 'e9aa246e508d99fb'
2018-01-09T22:41:25.407 <docker-entrypoint> INFO - Copied latest server-settings.example.json to /opt/factorio/config
2018-01-09T22:41:25.413 <docker-entrypoint> INFO - Copied latest map-gen-settings.example.json to /opt/factorio/config
2018-01-09T22:41:25.417 <docker-entrypoint> INFO - Using existing server-settings.json found in /opt/factorio/config
2018-01-09T22:41:25.422 <docker-entrypoint> INFO - Using existing map-gen-settings.json found in /opt/factorio/config
2018-01-09T22:41:25.430 <docker-entrypoint> WARN - No save.zip found in /opt/factorio/saves
2018-01-09T22:41:25.433 <docker-entrypoint> INFO - Creating new map / save.zip in /opt/factorio/saves with settings from /opt/factorio/config/map-gen-settings.json
FATAL: kernel too old

Note that restarting and redeploying the environment both result in the same error being repeated in the log. There are very few configuration options when pulling an image into a Jelastic host, so I don't know what I am able to change, if this is client error.

JyeGuru commented 6 years ago

Note: This seems to be something about the base linux image used, because it's affecting other Factorio docker containers as well.

goofball222 commented 6 years ago

@yukihyou I'm guessing this is actually an issue with the Jelastic Docker host kernel as Docker images don't load a kernel internally and instead are accessing the kernel and its functions from the host OS. You would need to reach out to their support to see what kernel and OS version they're running and see if there is any way they can put your services on a host with a newer version of the kernel.