"CannotStartContainerError: ResourceInitializationError" on Fargate 1.4.0

0

I have task that works fine using Fargate 1.3.0 but fails to start if I change the Platform version to 1.4.0 with this error message:

CannotStartContainerError: ResourceInitializationError: failed to create new container runtime task: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused "rootfs_linux.go:58:...

Any hints on how to go about debugging this?

asked 4 years ago1563 views
2 Answers
0

Is there a way to get the entire error message? It looks like anything helpful gets cut off in both the Console and the CLI:

"reason": "CannotStartContainerError: ResourceInitializationError: failed to create new container runtime task: OCI runtime create failed: container_linux.go:349: starting container process caused \"process_linux.go:449: container init caused \"rootfs_linux.go:58:...",
answered 4 years ago
0

It looks like I am running into a few issues with 1.4.0 but as far as I can tell this specific issue seems to be caused by trying to use the InitProcessEnabled LinuxParameter:

"LinuxParameters": {
  "Capabilities": {},
  "InitProcessEnabled": true
}

Is this no longer supported on Fargate 1.4.0?

answered 4 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions