OCI runtime exec failed: exec failed: container_linux.go:348

Product support balenaEngine
1

Hello Team,

We use your service on our two mainstream products,NUC and Jetson TX2.

On both devices we sometimes see random restarts of the containers. Recently I randomly captured the last stdout before the restart happens:

“OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused “process_linux.go:91: executing setns process caused "exit status 21"”: unknown”

Device info:

TYPE

Intel NUC

HOST OS VERSION

balenaOS 2.41.1+rev1

development

SUPERVISOR VERSION

10.2.2

I have seen a similar post here:

Do you think this has to do something with the supervisor or is it our Docker images?

I also found a popular post talking about this issue and the suggestion was the following:

use /bin/sh instead of /bin/bash

ref:

Before we start making changes to our Dockerfiles I wanted to have your opinion on this.

Thank you

2

Hi there, it’s difficult to say at this point, but these sorts of issues are typically (but not always) related to resource constraints on the device and possibly hardware issues with storage latency, etc. There could also be a problem with balena components, but we’d need to try and take a look at the device to see if we can narrow it down first. Are you able to grant support access and PM me the device guid (if you don’t want to make it public)?

6

I am encountering a similar problem:

OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "process_linux.go:93: starting setns process caused \"fork/exec /proc/self/exe: no such file or directory\"": unknown

This happens when I try to get a terminal to the device either through Balena Cloud UI or using balena cli tool (ssh).

Sometimes it seems restarting the container causes it to go away but then often it comes back.

Using balenaOS 2.58.6+rev1 on generic-x86-64
Supervisor version 11.14.0

7

I requested internal support and enabled support access on the device.