docker run ...command for each agent, the entire upgrade consists of running a few Docker commands - pull the latest image, stop and delete the existing agent container and recreate it with a freshly-download image. Such an upgrade is usually completed in a matter of seconds.
*.sqlitefiles into the new agent's data storage location
docker run ...command
sudo apt-get install te-va-unlockcommand
sudo systemctl stop te-agenton modern systems,
sudo stop te-agenton older systems such as Ubuntu 14.04 and RHEL 6.x
sudo systemctl disable te-agenton modern systems,
sudo update-rc.d -f te-agent removeon Ubuntu 14.04,
sudo chkconfig te-agent offon RHEL 6.x
/var/lib/te-agent/*.sqlitefiles to a temporary location, like your SSH user's home directory
docker run ...command above contains three paths that retain container's data and are bind-mounted into the container when it is running:
/var/lib/te-agentis the agent state directory, pointed out with #3 above, the one that we're interested in
/var/log/agentcontains agent logs
/var/lib/te-agentpath within the container has the following storage path on the host:
/docker-dataas a Host Vol. Agent Directory and the name
my-new-docker-agentas the name of the new Docker agent. This would give us the following default agent state storage path:
*.sqliteidentity files collected in Step #1b above should end up in.
*.sqliteidentity files into the created directory
*.sqlitefiles are owned by
te-agentdirectory, use the
*.sqliteidentity files into the target directory. If you are converting an existing package-based agent into a Docker-based one on the same host, you can simply use the
mvtool to move the files. If you are migrating the agent from another host, copy the files to the target host first (i.e. with the
scptool), then move them to the final location:
*.sqlitefiles - they need to be owned by the
/etc/te-agent.cfgfile has been collected. Let's inspect its content:
account-tokensetting is generally handled implicitly by the
docker run ...command generator below. However, pay attention to the
proxy-*settings - you may need to refer back to their values below.
proxy-*settings were configured, manipulate the proxy-related section of the dialog (3) to reach the identical proxy configuration.
docker run ...command will be generated (4). Pay particular attention to the
/var/lib/te-agentdirectory's storage path on the host (5) - the path should be identical to the one pre-created in Step #3 of this guide.
docker run ...command, run it on your new host. Continuing with the existing example, the following commands should be run to create and start the new Docker agent: