When starting a set container possibility to be able to group them.
The benefit this would be that when executing plugins the group ID would be enough to execute
plugin in a set of containers. This provides the possibility to execute repetitive tasks in containers in
a single cli command. To store groups there is a file called grouptrackcontainer.json which tracks all
the groups currently present set by the client. The snippet below
show a sample structure of file grouptrackcontainer.json.
The group id will be auto-generated and will will have it's own prefix in the start which will mostly be grp<uuid>.
When a container is removed using the command. p2prc --rm <ip address> --id <container id>. It will be automatically deleted from the groups it exists in.
Grouping Containers
When starting a set container possibility to be able to group them. The benefit this would be that when executing plugins the group ID would be enough to execute plugin in a set of containers. This provides the possibility to execute repetitive tasks in containers in a single cli command. To store groups there is a file called
grouptrackcontainer.json
which tracks all the groups currently present set by the client. The snippet below show a sample structure of filegrouptrackcontainer.json
.The default path to the container tracker is
client/trackcontainers/grouptrackcontainer.json
.Sample commands
Note:
The group id will be auto-generated and will will have it's own prefix in the start which will mostly be
grp<uuid>
.When a container is removed using the command.
p2prc --rm <ip address> --id <container id>
. It will be automatically deleted from the groups it exists in.