Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
2.7 GA
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Sprint 2020-57, integration-doc-2020-01-27, integration-doc-2020-02-17, integration-doc-2020-03-09, integration-doc-2020-03-30
Description
Following the documentation about managing toolbox remotes, I create a new toolbox remote:
$ docker run registry.redhat.io/3scale-amp2/toolbox-rhel7:3scale2.7 3scale remote add instance_a https://123456789@example_a.net
The command succeeded.
Later when I want to use the remote in another command, the remote does not exist. For instance, if I want to list my remotes
$ docker run registry.redhat.io/3scale-amp2/toolbox-rhel7:3scale2.7 3scale remote list Empty remote list.
This is a docker issue. Every run of docker command creates a new container and storage (where remotes exist) is gone.
WE could tell customers to create remotes, commit the docker container (create image out of a container) and then run the new image with remote info included.
$ docker run --name toolbox-container registry.redhat.io/3scale-amp2/toolbox-rhel7:3scale2.7 3scale remote add instance_a https://123456789@example_a.net $ docker commit toolbox-container toolbox $ docker run toolbox 3scale remote list instance_a https://example_a.net 123456789
Any other toolbox command, if using remotes, the newly created image should be used, i.e. `toolbox` instead of `registry.redhat.io/3scale-amp2/toolbox-rhel7:3scale2.7`