During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos containerinstances
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos containerinstances --help prints.
For more information see Chaos Engineering and Container Instances Emulator.
locally chaos containerinstances
Simulate Container Instances (data plane) failure modes.
Simulate Container Instances (data plane) failure modes. A fault command sets the fault's rate. With a scope flag (--location / --name) it adds or edits a rule instead. Examples: locally chaos containerinstances <fault> --percentage N locally chaos containerinstances <fault> reset locally chaos containerinstances show locally chaos containerinstances reset
Usage
locally chaos containerinstances [flags] locally chaos containerinstances [command]
Flags
-h, --help[=true|false] help for containerinstances
Subcommands
- locally chaos containerinstances disconnect - Close live connections cleanly.
- locally chaos containerinstances drop-connection - Reset new connections before they reach the container.
- locally chaos containerinstances exit - Kill container groups on a schedule, as a crash would.
- locally chaos containerinstances freeze - Pause container groups on a schedule.
- locally chaos containerinstances incident - Take each resource down for a while, then bring it back.
- locally chaos containerinstances latency - Delay new connections by a random time before the container is dialled.
- locally chaos containerinstances outage - Refuse new connections: each is accepted and reset before a byte reaches the container, so the client sees ECONNRESET.
- locally chaos containerinstances reset - Zero every Container Instances (data plane) fault and drop every rule.
- locally chaos containerinstances restart - Restart container groups on a schedule.
- locally chaos containerinstances show - Print the current Container Instances (data plane) chaos configuration.
locally chaos containerinstances disconnect
Close live connections cleanly.
Close live connections cleanly. Every interval each open connection is rolled for; on a hit it is closed with a FIN, an orderly TCP close the client reads as end of stream. Compare drop-connection, which resets it. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances disconnect --percentage 25 --interval 10m locally chaos containerinstances disconnect --percentage 100 --interval 10m --location london locally chaos containerinstances disconnect reset --location london locally chaos containerinstances disconnect --percentage 100 --interval 10m --name acct1
Usage
locally chaos containerinstances disconnect [flags] locally chaos containerinstances disconnect [command]
Flags
-h, --help[=true|false] help for disconnect
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances disconnect reset - Remove one disconnect rule, or put the whole fault back to zero.
locally chaos containerinstances disconnect reset
Remove one disconnect rule, or put the whole fault back to zero.
Reset the disconnect fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances disconnect reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances drop-connection
Reset new connections before they reach the container.
Reset new connections before they reach the container. The client sees ECONNRESET, with nothing sent. With --interval it also cuts live connections: every interval each is rolled for, and on a hit it is reset with nothing said - no close frame or goodbye. For a clean close, use disconnect. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval adds periodic action on live connections, such as every 30s, to the fault's per-request behaviour, which carries on as before. For periodic cuts with no per-request drops, arm disconnect instead. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances drop-connection --percentage 25 locally chaos containerinstances drop-connection --percentage 25 --interval 30s locally chaos containerinstances drop-connection --percentage 100 --location london locally chaos containerinstances drop-connection reset --location london locally chaos containerinstances drop-connection --percentage 100 --name acct1
Usage
locally chaos containerinstances drop-connection [flags] locally chaos containerinstances drop-connection [command]
Flags
-h, --help[=true|false] help for drop-connection
--interval string Also act on live connections this often, e.g. 30s or 10m (adds to the per-request fault; use disconnect for periodic cuts only)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos containerinstances drop-connection reset
Remove one drop-connection rule, or put the whole fault back to zero.
Reset the drop-connection fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances drop-connection reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances exit
Kill container groups on a schedule, as a crash would.
Kill container groups on a schedule, as a crash would. Every interval each group is rolled for; on a hit its containers get SIGKILL and the group's restart policy decides what happens next: Always restarts them, Never leaves them exited with code 137. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances exit --percentage 25 --interval 10m locally chaos containerinstances exit --percentage 100 --interval 10m --location london locally chaos containerinstances exit reset --location london locally chaos containerinstances exit --percentage 100 --interval 10m --name acct1
Usage
locally chaos containerinstances exit [flags] locally chaos containerinstances exit [command]
Flags
-h, --help[=true|false] help for exit
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances exit reset - Remove one exit rule, or put the whole fault back to zero.
locally chaos containerinstances exit reset
Remove one exit rule, or put the whole fault back to zero.
Reset the exit fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances exit reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances freeze
Pause container groups on a schedule.
Pause container groups on a schedule. Every interval each group is rolled for; on a hit every container in it is paused (as docker pause does) for the rolled duration, then unpaused. Processes stop where they are and carry on afterwards; nothing is closed, so open connections just go quiet. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. One value N picks 0 to N each time; MIN-MAX, such as 30-120, picks within that range. A duration is required whenever the fault fires. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances freeze --percentage 25 --seconds 30-120 --interval 10m locally chaos containerinstances freeze --percentage 100 --seconds 30-120 --interval 10m --location london locally chaos containerinstances freeze reset --location london locally chaos containerinstances freeze --percentage 100 --seconds 30-120 --interval 10m --name acct1
Usage
locally chaos containerinstances freeze [flags] locally chaos containerinstances freeze [command]
Flags
-h, --help[=true|false] help for freeze
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--millis string Duration in milliseconds, e.g. 250; N for 0 to N, or MIN-MAX for a range
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; N for 0 to N, or MIN-MAX for a range
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances freeze reset - Remove one freeze rule, or put the whole fault back to zero.
locally chaos containerinstances freeze reset
Remove one freeze rule, or put the whole fault back to zero.
Reset the freeze fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances freeze reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances incident
Take each resource down for a while, then bring it back.
Take each resource down for a while, then bring it back. Every interval each resource (or, on the directory and identity surfaces, the tenant) rolls against the percentage; on a hit every request to it fails for the rolled duration, answered as an outage would be, then it recovers on its own. Compare outage, which fails requests for as long as it is armed. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. One value N picks 0 to N each time; MIN-MAX, such as 30-120, picks within that range. A duration is required whenever the fault fires. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances incident --percentage 25 --seconds 30-120 --interval 10m locally chaos containerinstances incident --percentage 100 --seconds 30-120 --interval 10m --location london locally chaos containerinstances incident reset --location london locally chaos containerinstances incident --percentage 100 --seconds 30-120 --interval 10m --name acct1
Usage
locally chaos containerinstances incident [flags] locally chaos containerinstances incident [command]
Flags
-h, --help[=true|false] help for incident
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--millis string Duration in milliseconds, e.g. 250; N for 0 to N, or MIN-MAX for a range
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; N for 0 to N, or MIN-MAX for a range
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances incident reset - Remove one incident rule, or put the whole fault back to zero.
locally chaos containerinstances incident reset
Remove one incident rule, or put the whole fault back to zero.
Reset the incident fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances incident reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances latency
Delay new connections by a random time before the container is dialled.
Delay new connections by a random time before the container is dialled. Once connected, traffic flows as usual. With --interval it also stalls live connections: every interval each is rolled for, and on a hit nothing crosses it in either direction until the rolled delay has passed. Nothing is dropped; it all arrives late. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. The value is a maximum: each firing picks 0 to N. A duration is required whenever the fault fires. --interval adds periodic action on live connections, such as every 30s, to the fault's per-request behaviour, which carries on as before. For periodic cuts with no per-request drops, arm disconnect instead. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances latency --percentage 25 --seconds 30 locally chaos containerinstances latency --percentage 25 --seconds 30 --interval 30s locally chaos containerinstances latency --percentage 100 --seconds 30 --location london locally chaos containerinstances latency reset --location london locally chaos containerinstances latency --percentage 100 --seconds 30 --name acct1
Usage
locally chaos containerinstances latency [flags] locally chaos containerinstances latency [command]
Flags
-h, --help[=true|false] help for latency
--interval string Also act on live connections this often, e.g. 30s or 10m (adds to the per-request fault; use disconnect for periodic cuts only)
--location string Scope this rule to one location, e.g. london
--millis string Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos containerinstances latency reset
Remove one latency rule, or put the whole fault back to zero.
Reset the latency fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances latency reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances outage
Refuse new connections: each is accepted and reset before a byte reaches the container, so the client sees ECONNRESET.
Refuse new connections: each is accepted and reset before a byte reaches the container, so the client sees ECONNRESET. When the outage starts, every connection already open is closed once. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos containerinstances outage --percentage 25 locally chaos containerinstances outage --percentage 100 --location london locally chaos containerinstances outage reset --location london locally chaos containerinstances outage --percentage 100 --name acct1
Usage
locally chaos containerinstances outage [flags] locally chaos containerinstances outage [command]
Flags
-h, --help[=true|false] help for outage
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos containerinstances outage reset
Remove one outage rule, or put the whole fault back to zero.
Reset the outage fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances outage reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances reset
Zero every Container Instances (data plane) fault and drop every rule.
Zero every Container Instances (data plane) fault and drop every rule. Examples: locally chaos containerinstances reset
Usage
locally chaos containerinstances reset [flags]
Flags
-h, --help[=true|false] help for reset
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances restart
Restart container groups on a schedule.
Restart container groups on a schedule. Every interval each group is rolled for; on a hit its containers are stopped and started again, dropping their connections. Without scope flags this sets the fault's rate on Container Instances (data plane). With --location / --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos containerinstances restart --percentage 25 --interval 10m locally chaos containerinstances restart --percentage 100 --interval 10m --location london locally chaos containerinstances restart reset --location london locally chaos containerinstances restart --percentage 100 --interval 10m --name acct1
Usage
locally chaos containerinstances restart [flags] locally chaos containerinstances restart [command]
Flags
-h, --help[=true|false] help for restart
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos containerinstances restart reset - Remove one restart rule, or put the whole fault back to zero.
locally chaos containerinstances restart reset
Remove one restart rule, or put the whole fault back to zero.
Reset the restart fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos containerinstances restart reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos containerinstances show
Print the current Container Instances (data plane) chaos configuration.
Print the current Container Instances (data plane) chaos configuration. Examples: locally chaos containerinstances show
Usage
locally chaos containerinstances show [flags]
Flags
-h, --help[=true|false] help for show
--subscription string Subscription UUID (defaults to the configured default)
During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in