Skip to content

Commit f6cf94d

Browse files
authored
"IoT Edge runtime in a container" section removed
1 parent 4990608 commit f6cf94d

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

articles/iot-edge/development-environment.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -98,11 +98,6 @@ The Azure IoT Edge dev container is a Docker container that has all the dependen
9898

9999
For more information, see [Azure IoT Edge dev container](https://github.com/Azure/iotedgedev/wiki/quickstart-with-iot-edge-dev-container).
100100

101-
### IoT Edge runtime in a container
102-
103-
The IoT Edge runtime in a container provides a complete runtime that takes your device connection string as an environment variable. This container enables you to test IoT Edge modules and scenarios on a system that may not support the runtime natively, like macOS. Any modules that you deploy will be started outside of the runtime container. If you want the runtime and any deployed modules to exist within the same container, consider the IoT Edge device container instead.
104-
105-
106101
### IoT Edge device container
107102

108103
The IoT Edge device container is a complete IoT Edge device, ready to be launched on any machine with a container engine. The device container includes the IoT Edge runtime and a container engine itself. Each instance of the container is a fully functional self-provisioning IoT Edge device. The device container supports remote debugging of modules, as long as there is a network route to the module. The device container is good for quickly creating large numbers of IoT Edge devices to test at-scale scenarios or Azure Pipelines. It also supports deployment to kubernetes via helm.

0 commit comments

Comments
 (0)