Facing docker error while creating environment in beanstalk

[dummyuser-123]

Hi,

Actually, I am deploying an ML model using Docker in Beanstalk. Firstly, I uploaded my Docker image (which contains my ML model) to Docker Hub. Then, I deployed it into Beanstalk using docker-compose.yml. In Beanstalk, I am using Docker as a platform, and my model requires GPU support. For that, I have used the Deep Learning AMI GPU CUDA 11.5.2 (Amazon Linux 2) 20230104, which is built with NVIDIA CUDA, cuDNN, NCCL, GPU Driver, Docker, NVIDIA-Docker, and EFA support. However, when I am building the environment using this configuration, I encounter the following error:

[ERROR] An error occurred during execution of command [app-deploy] - [Track pids in healthd]. Stop running the command. Error: update processes [docker eb-docker-compose-events eb-docker-compose-log eb-docker-events cfn-hup healthd] pid symlinks failed with error read pid source file /var/pids/docker.pid failed with error:open /var/pids/docker.pid: no such file or directory.

Means my environment is building but it is giving the error message like: Env build successfully but with some errors. I found this error message in the eb.engine.log. Additionally, when I checked the EC2 instance through SSH, it showed that NVIDIA drivers, NVIDIA CUDA, and Docker are already installed (verified using these commands: nvidia-smi, docker -v). I have tried multiple different deep learning AMIs, but I encounter the same issue with all of them. Also, I noticed a strange thing while trying out different AMIs: if I build the environment with default settings like Docker platform with the default Docker AMI, it builds successfully without any error. However, when I pass a different AMI ID in the configuration, it is not able to build the environment properly.

I am new to AWS Elastic Beanstalk, but I have thoroughly read the official Beanstalk documentation. Despite this, I believe I may be missing something during environment creation. Does anyone know how to solve this error?

[dsapab]

Hello @dummyuser-123, thanks for reaching out!

It looks like there might be an issue when starting the Docker container. Without seeing the exact logs, it would be hard to know but I would like to try and reproduce the issue. Could you please provide me:

1. Exact Beanstalk platform you are using.
2. AMI ID and AWS Region where you tried
3. Is there any public/sample Docker image that I can use to test? You may also share a Docker compose and any Dockerfiles.

note Please remove any sensitive information or anything your consider internal/confidential.

I would like to try and reproduce the behaviour. I suspect there might a driver/component missing that your Docker image requires.

Thanks!