ON THIS PAGE

DID THIS PAGE HELP YOU?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Troubleshooting Dynamic Engine pods stuck in ContainerCreating status

Resolve mount-related errors when Dynamic Engine pods fail to start and remain in ContainerCreating status on Amazon EKS with Amazon EFS.

Pods fail to start and remain in ContainerCreating status with mount-related errors in pod events.

Verify mount targets in all private subnets where the nodes run.
Use the AWS Management Console or the following AWS CLI command:
```
aws efs describe-mount-targets --file-system-id <EFS_ID>
```
The output should show one mount target for each subnet where your nodes run.
Verify that the EFS security group allows inbound NFS traffic on TCP port 2049.
In the AWS Management Console, verify the EFS security group rules. NFS traffic on TCP port 2049 must originate from the worker node security group.
Verify that route tables for private subnets contain routes to the subnets hosting EFS mount targets.

Network ACLs should allow NFS traffic on TCP port 2049 in both directions.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!