AWS Deepracer DRFC MinIO Fixes

In this guide, we address common issues and resolutions related to the dr-upload-custom-files operation when working with DeepRacer DRFC repo, Docker and MinIO. Repo Link: https://github.com/aws-deepracer-community/deepracer-for-cloud Whether you encounter swarm manager errors, container conflicts, or bucket-related issues, this document provides troubleshooting steps to ensure a smooth process. Additionally, key verification commands are included to assist with system diagnostics and resolution. Error when dr-upload-custom-files "Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again." Check docker ps -a Steps to fix docker run -d -p 9000:9000 --name minio minio/minio:RELEASE.2022-10-24T18-35-07Z s If you're unlucky enough (as I was) to get the following messgae Try again "dr-upload-custom-files" Then try either 1 or both of the below scenarios. Scenario A: If you get the below error docker: Error response from daemon: Conflict. The container name "/minio" is already in use by container "75734681ee2c1ec634a7f6f928e8db93d077bdb289d6435af9e9b7a3bc113ff4". You have to remove (or rename) that container to be able to reuse that name. Run following docker ps -a docker start minio docker start s3_minio.1.vwyypz7jhdj9d16h0db2kzwh1 Scenario B: If you get the below error Uploading files to s3://bucket/custom_files/ fatal error: An error occurred (NoSuchBucket) when calling the ListObjectsV2 operation: The specified bucket does not exist TBD - Could have to migrate to a current minio Extra Info / Verification Check system.env (DR_MINIO_IMAGE in system.env, make sure it’s set to: RELEASE.2022–10–24T18–35–07Z docker service ls (Make sure you see s3_minio) docker stack ls ("Should return "s3, services 1") docker logs "container id from docker ps -a" dr-local-aws s3 ls

Feb 25, 2025 - 16:48

In this guide, we address common issues and resolutions related to the dr-upload-custom-files operation when working with DeepRacer DRFC repo, Docker and MinIO.

Repo Link: https://github.com/aws-deepracer-community/deepracer-for-cloud

Whether you encounter swarm manager errors, container conflicts, or bucket-related issues, this document provides troubleshooting steps to ensure a smooth process. Additionally, key verification commands are included to assist with system diagnostics and resolution.

Error when dr-upload-custom-files
"Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again."

Check
docker ps -a

Steps to fix
docker run -d -p 9000:9000 --name minio minio/minio:RELEASE.2022-10-24T18-35-07Z s

If you're unlucky enough (as I was) to get the following messgae
Try again "dr-upload-custom-files" Then try either 1 or both of the below scenarios.

Scenario A: If you get the below error
docker: Error response from daemon: Conflict. The container name "/minio" is already in use by container "75734681ee2c1ec634a7f6f928e8db93d077bdb289d6435af9e9b7a3bc113ff4". You have to remove (or rename) that container to be able to reuse that name.

Run following
docker ps -a
docker start minio
docker start s3_minio.1.vwyypz7jhdj9d16h0db2kzwh1

Scenario B: If you get the below error
Uploading files to s3://bucket/custom_files/
fatal error: An error occurred (NoSuchBucket) when calling the ListObjectsV2 operation: The specified bucket does not exist

TBD - Could have to migrate to a current minio

Extra Info / Verification
Check system.env (DR_MINIO_IMAGE **in system.env, make sure it’s set to:
**RELEASE.2022–10–24T18–35–07Z

docker service ls (Make sure you see s3_minio)
docker stack ls ("Should return "s3, services 1")

docker logs "container id from docker ps -a"
dr-local-aws s3 ls