Halite Home

Bot error due to docker

#1

In this game my bot errors on init.

However, the error log contains

/usr/bin/docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:245: running exec setns process for init caused \\\"exit status 6\\\"\"\n".

It would seem that this is a problem with the docker instance, not my code.

#2

I've gotten the same error on my bot. Seems very intermittent.

#3

This happened to me as well in
https://2016.halite.io/game.php?replay=ar1481787421-2230225494.hlt
it looks like multiple bots faced the same problem in this match as 4 of the 6 bots do not get past turn one.

log contains the exact same information as stated by @cg505

#4

I have got the same error just now.

#5

I have also encountered the same problem.

#6

This has happened a couple times in the past few weeks. We are looking into the root cause of the error.

Around 6:30 EST, this morning, we restarted all of our game servers, which fixed the problem for now.

#7

Just got another one, perhaps even more entertaining:

sh: 1: /usr/bin/docker: not found
#8

Thank you so much for the report.

Took that worker offline. Looking into the root cause.

#9

To help investigate the root cause: I had it happen to me to here:
https://2016.halite.io/game.php?replay=ar1482230084-2510848161.hlt

/usr/bin/docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:245: running exec setns process for init caused \\\"exit status 6\\\"\"\n".

#10

Same issue here

     --- Init ---
/usr/bin/docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:245: running exec setns process for init caused \\\"exit status 6\\\"\"\n".
 --- Bot used 0 milliseconds ---
-----------------------------------------------------------------------------
 --- Frame #1 ---

ERRORED!
No response received.

Seems to happen like once ever 10 games or so. Bot just dies round 1.

#11

And here. Got my first error like this at 12/19/2016, 11:13:04 PM, on a bot I submitted 12/17/2016, 10:02:26 AM. Since then, it's happened at 3:56 AM, 4:47 AM, and 9:54 AM today.

 --- Init ---
/usr/bin/docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:245: running exec setns process for init caused \\\"exit status 6\\\"\"\n".
 --- Bot used 2368 milliseconds ---
-----------------------------------------------------------------------------
 --- Frame #1 ---

ERRORED!
No response received.
#12

I've seen too, Bots getting killed in the first round, and something after 3 or 4 steps, with this same error. Could be this problems with server scalation? I hope it is solved quickly for the sake and fairness of this game.

#14

Bump - i see messages like these:

--- Init ---
/usr/bin/docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:245: running exec setns process for init caused \\"exit status 6\\"\"\n".
--- Bot used 2280 milliseconds ---

--- Frame #1 ---

ERRORED!
No response received.

#15

I am receiving this error frequently this evening.

--- Init ---
/usr/bin/docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:245: running exec setns process for init caused \\"exit status 6\\"\"\n".
--- Bot used 1928 milliseconds ---

--- Frame #1 ---

ERRORED!
No response received.

#16

I got the same error as well.