Frequently asked questions

How do I stop my containers?

To stop the containers used by analyze-deployment-tooling, run:

manage-environment -t stop

Note: This will stop the VS Code Dev Container where you run the command. You can close VS Code without reloading the window.

For more information, see Stopping the environment.

How do I restart my containers?

To restart the environment, run the deploy command with the name of the config that you want to start. For example:

deploy

If you have multiple configs, specify the config name with -c <config-name>.

For more information, see Deploying your config in the environment.

How do I access the system?

To connect to the deployment, the URL to use is: https://i2analyze.eia:9443/opal

Note: If you are using the schema_dev or i2c deployment patterns, you must connect using Analyst's Notebook.

If you are using a VM to connect to your deployment, you might need to ensure that your hosts file is still configured correctly. For more information, see Set up development environment.

How do I log in to i2 Analyze?

Log in as a user that is specified in the user registry file. If you are using the example user registry, the example user has the following credentials:

The user name is Jenny
The password is Jenny

How do I recover disk space?

As you develop configurations and upgrade your system this can cause Docker to use a large amount of disk space on your server for now unused images and containers.

Before you clear any data from your system, perform a back up of any databases in your configs. To backup the databases in all of your configs, run:
```
manage-environment -t backup -b <backup-name>
```
For more information about backing up your data, see Backup and restore.
Docker provides commands to remove any unused containers, networks, and images from your system.

Warning: This will remove all unused Docker artifacts, not just the ones associated with analyze-deployment-tooling. Alternatively you can use Docker Desktop to manually delete the analyze-deployment-tooling artifacts.
```
docker system prune
```
For more information, see docker system prune.

How do I uninstall analyze-deployment-tooling?

To completely remove analyze-deployment-tooling from your system, stop and remove all Docker artifacts then delete the analyze-deployment-tooling data from your disk. Additionally you can uninstall VS Code and Docker Desktop.

To stop the containers used by analyze-deployment-tooling, run:
```
manage-environment -t stop
```
For more information, see Stopping the environment.
Docker provides commands to remove any unused containers, networks, images, and volumes from your system.

Warning: This will remove all unused Docker artifacts, not just the ones associated with analyze-deployment-tooling. Alternatively you can use Docker Desktop to manually delete the analyze-deployment-tooling artifacts.

From your local terminal, run:
```
docker system prune --all --volumes
```
For more information, see docker system prune.
Delete your analyze-deployment-tooling folder and its contents.
To uninstall VS Code, see Uninstall Visual Studio Code.
To uninstall Docker Desktop, see Uninstall Docker Desktop.