Containers Starting and stopping the container
IX30 User Guide
814
8. Save the configuration and apply the change:
(config network wireless client new_client)> save
Configuration saved.
>
9. Type exit to exit the Admin CLI.
Depending on your device configuration, you may be presented with an Access selection
menu. Type quit to disconnect from the device.
Starting and stopping the container
Container commands are not available from the Admin CLI. You must access the device shell in order
to run Python applications from the command line. See Authentication groups for information about
configuring authentication groups that include shell access.
Note Container support must be enabled in Digi Remote Manager. Contact your Digi sales
representative for information.
Starting the container
There are two methods to start containers:
n
Non-persistent: Changes made to the container file system will be lost when the container is
stopped.
n
Persistent: Changes made to the container file system when not be lost when the container is
stopped.
Starting a container in non-persistent mode
To start the container in non-persistent mode:
1. Select a device in Remote Manager that is configured to allow shell access to the admin user,
and click Actions > Open Console. Alternatively, log into the IX30 local command line as a user
with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, type:
# lxc container_name
lxc #
where container_name is the name of the container as configured on the device. For example:
# lxc test_lxc
lxc #
This will start the container by using /bin/sh -l, which runs the shell and loads the shell profile. The
default shell profile includes an lxc # prompt.
Starting a container in persistent mode
To start the container in persistent mode, include the -p option at the command line. For example:
To Next Page
Loading...
Need help?
General
