You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/learn/develop/multicontainer.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,11 +115,11 @@ In addition to the settings above, there are some {{ $names.company.lower }} spe
115
115
116
116
### Container requirements
117
117
118
-
**Note** Container requirements are available when using balenaCLI >= 21.1.0
118
+
**Note:** Container requirements are available when using balenaCLI >= 21.1.0
119
119
120
-
An additional set of labels allows to ensure the compatibility of a device when it comes to run a service. For example, before updating to a new release, it may be desirable to ensure that the device is running a specific version of [Supervisor][supervisor] or has a specific version of the [NVIDIA Tegra Linux Driver Package][l4t] (L4T).
120
+
An additional set of labels ensures device compatibility for running a service. For example, before updating to a new release, it may be desirable to ensure that the device is running a specific version of [Supervisor][supervisor] or has a specific version of the [NVIDIA Tegra Linux Driver Package][l4t] (L4T).
121
121
122
-
The following set of requirement labels are enforced via the supervisor. Each service may define one or more requirements and if any of them is not met for any non-[optional](#optional-containers) service, then the release will be **rejected** and no changes will be performed for the new release.
122
+
The following set of requirement labels are enforced via the supervisor. Each service may define one or more requirements and if any of them is not met for any non-[optional](#optional-containers) service, then [the release will be rejected][update-statuses] and no changes will be performed for the new release.
**Note** When updating between releases, if the new version of and optional service has unmet requirements, the old version of the service will still be killed.
166
+
**Note:** When updating between releases, if the new version of and optional service has unmet requirements, the old version of the service will still be killed.
0 commit comments