After applying the deployment manifest sudo az iot edge set-modules --hub-name "$IOT_HUB_NAME" --device-id "$DEVICE_ID" --content "$MANIFEST_FILE_PATH_RUNNING" --only-show-error -o table the Agent fails to initialize container from private repository. The container remains in created state although the manifest defines the container's status as "running". Credentials for the repo are indeed provided in the properties.desired of edgeAgent

Hello @Omar Navarro , you are deploying a deployment manifest to an Azure IoT Edge device. This deployment manifest describes (among other things) which docker containers should be deployed, complete with environment variables, and create options and module twin. The edge device will load the containers from registries as described in the manifest. If the registry is secured, you must provide registry credentials in the deployment manifest too, as seen in the message. In the Azure portal, adding credentials is easy: This will end up in the deployment manifest as part of the desired properties of the edgeAgent: You can find the secret as Access keys:

Azure IoT Edge fails to start module from private repo

Accepted answer

Sander van de Velde | MVP 32,556 Reputation points MVP

2022-07-23T08:56:15.757+00:00

Hello @Omar Navarro ,

you are deploying a deployment manifest to an Azure IoT Edge device.

This deployment manifest describes (among other things) which docker containers should be deployed, complete with environment variables, and create options and module twin.

The edge device will load the containers from registries as described in the manifest.

If the registry is secured, you must provide registry credentials in the deployment manifest too, as seen in the message.

In the Azure portal, adding credentials is easy:

This will end up in the deployment manifest as part of the desired properties of the edgeAgent:

You can find the secret as Access keys:
Please sign in to rate this answer.
Omar Navarro 331 Reputation points

2022-07-23T19:00:25.297+00:00

Here is the moment in the log which seems to fail at initializing the container

Sander van de Velde | MVP 32,556 Reputation points MVP

2022-07-23T19:17:35.997+00:00

Hello @Omar Navarro ,

it seems the credentials are added to the deployment manifest.

Next, check the log of the edgeAgent. The edgeAgent will also show the reason why a module cannot be loaded or started.

Can you confirm the container is pulled from the container registry?

you can check the local repo:

sudo docker images

This will list the modules, all already pulled.

If so, you can also check possible logging of your container (if the container does not start that well, this logging is probably empty):

sudo iotedge logs -f workflowengine

Omar Navarro 331 Reputation points

2022-07-23T20:20:45.31+00:00

Thank you for the response. The issue was that docker resources needed to be cleared before applying the new template.

like so:

# Stop all containers sudo docker stop `sudo docker ps -qa` # Remove all containers sudo docker rm -f `sudo docker ps -qa` # Remove all images sudo docker rmi -f `sudo docker images -qa ` # Remove all networks sudo docker network rm -f `sudo docker network ls -q`

issue is resolved.

Sander van de Velde | MVP 32,556 Reputation points MVP

2022-07-23T20:33:32.587+00:00

Hello @Omar Navarro ,

good to read you managed to fix this issue.

Azure IoT Edge is able to update modules as long the id is incremented (as in: differs from a previous deployment manifest entry).

If a 'old' container is renewed without changing the name (or a reused name), and the container with the old name was already pulled into the local repository, Azure IoT Edge will ignore/not recognize the update. So the old container stays unmodified in the local repository.

----------

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, all community members who have a similar issue will benefit. Your contribution is highly appreciated.

Omar Navarro 331 Reputation points

2022-10-19T20:00:01.46+00:00

Is there a recommended approach with Edge to always update the modules (without incrementing)

Sander van de Velde | MVP 32,556 Reputation points MVP

2022-10-19T22:08:42.25+00:00

Hello @Omar Navarro ,

the recommended way to update modules is using incremental tags for modules.

The edgeAgent/runtime compares deployment updates with the current versions in the local repository on the edge device.

If you want to reuse the same tag, you need to remove the previous version from the local repo first.

---

Thanks for asking these questions.

Please create a new question instead of adding extra questions to existing threads (with an unrelated topic). This adds value to the forum because the new questions are discoverable by others and it gives credit to those answering them.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure IoT Edge fails to start module from private repo

0 additional answers

Your answer