Azure / Azure/iotedgedev

[BUG] Simulator not respecting docker status of stopped

Open
#600 2 comments 0 reactions 0 assignees View on GitHub
bug InBacklog
Dominant language
Python
Stars
166
Forks
76
PR merge metrics
No merged PRs in 30d

Description

### Description

Simulator is not respecting docker status of stopped and is creating and starting containers for modules that have status set as stopped `"status": "stopped",`
```
"modules": {
"MyModule": {
"version": "1.0.0",
"type": "docker",
"status": "stopped",
"restartPolicy": "never",
"settings": {
"image": "imagename",
"createOptions": {}
}
}
}
```

### Expected behavior

Simulator start should only create but not start containers for modules that have status set as stopped `"status": "stopped",`

### Actual behavior

Simulator start is creating and starting containers for modules that have status set as stopped `"status": "stopped",`

### Steps to Reproduce

A deployment manifest with a stopped module
```
"modules": {
"MyModule": {
"version": "1.0.0",
"type": "docker",
"status": "stopped",
"restartPolicy": "never",
"settings": {
"image": "imagename",
"createOptions": {}
}
}
}
```
`sudo iotedgedev simulator start`

### Environment

iotedgedev, version 3.3.7
Python 3.7.15
pip 22.3.1 from /usr/local/lib/python3.7/dist-packages/pip (python 3.7)
WSL2 Ubuntu 22.04

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.