Docker Containeroption selected.
Ubuntu 14.04.x LTS, the operating system that was used as a base for the previous Docker image, is currently reaching the end-of-life stage.
docker run ...command is used to create a new container
docker run ...command, or being able to recreate it.
docker run ...command. If you already have the original
docker run ...command, skip the following section that deals with ways to regenerate the lost
docker run ...command and head directly to the section below describing redeployment steps.
docker run ...command that was used to create the agent container, you will need to recreate it. The solutions presented below are not the universal silver bullet to address this issue with 100% accuracy, yet they will provide sufficient tools and methods that you can use to achieve your goal and come up with a
docker run ...command that is sufficiently similar to the one that was used initially.
docker run ...command, or the best approximation it can come up with. This tool is called
runlikeutility with the following commands:
runlikecommand by providing it a name of the container it should inspect and recreate the
docker run ...command for:
--ip=10.5.2.226part, which is probably due to manual IP assignment being a fairly uncommon thing in the Docker world.
runliketool generates the relevant output by inspecting the output of the
docker inspectcommand. You are encouraged to:
docker inspectyourself, to make sure something important has not been missed out, and
docker inspectoutput of the running container for the post-upgrade verification.
docker inspectoutput, run the following command:
docker inspectoutput in the file called
my-container-name.inspect.ORIG, located in the current directory.
docker run ...command consists of the following steps:
docker run ...command version
docker run ...command for deploying Docker-based Enterprise Agent is waiting for you:
docker inspectoutput file you created earlier to determine this value.
docker run ...command (3) for you. From here on, the effort to recreate an identically configured container is a matter of trial an error:
docker inspectfile using the
docker inspect my-agent-name > my-agent-name.inspect.NEWcommand
difftool to compare the original and new
docker run ...command and go back to step #1
docker run ...command at hand, you are still encouraged to store the current running container's
docker inspectoutput for later inspection and comparison with the inspect output from the newly created container. You can store the running container's docker inspect output with the following command:
thousandeyes/enterprise-agentbase image. Proceed to the post-redeployment tasks section below for the final touches.
docker run ...command generally takes care of all aspects of container configuration. The only remaining task that is currently not handled during the container creation is the installation of your internal CA certificates on your new agents. For further information, see the Docker-related section of the CA certificate installation guide.