Tag the fresh container images as `latest` before exporting them
```shell
docker image tag "reseed-app:latest""reseed-app:${DOCKER_IMAGE_TAG}"
docker image tag "reseed-web:latest""reseed-web:${DOCKER_IMAGE_TAG}"
docker image tag "reseed-workers:latest""reseed-workers:${DOCKER_IMAGE_TAG}"
```
ℹ Tagging the images as `latest` on the builder VM makes life easier when exporting/copying them over to the actual ReSeeD VM on which they will run, because this eliminates the need for one error-prone "copy $DOCKER_IMAGE_TAG string to another machine" operation.
Transfer the container images to the desired ReSeeD / docker host as described on the ["Transferring Images" page](/system/deployment/3_Transferring_Images).
**Table of Contents**
---
This page extends the information from the ["Building container images" page](/system/deployment/Building-Container-Images).
---
#### How to build images for ReSeeD
Connect to the builder VM:
```shell
export BUILD_USER="builder"
export BUILD_HOST="builder.example.net"
ssh "${BUILD_USER}@${BUILD_HOST}"
```
If the VM is running *low on free storage space*, remove the *latest* images (specifically the images themselves, not just the image tags):
```shell
df-h# Check disk usage
docker image ls
# Multiple image ids (or "imagename:imagetag" strings) can be supplied at the same time
Tag the fresh container images as `latest` before exporting them
```shell
docker image tag "reseed-app:latest""reseed-app:${DOCKER_IMAGE_TAG}"
docker image tag "reseed-web:latest""reseed-web:${DOCKER_IMAGE_TAG}"
docker image tag "reseed-workers:latest""reseed-workers:${DOCKER_IMAGE_TAG}"
```
ℹ Tagging the images as `latest` on the builder VM makes life easier when exporting/copying them over to the actual ReSeeD VM on which they will run, because this eliminates the need for one error-prone "copy $DOCKER_IMAGE_TAG string to another machine" operation.
Transfer the container images to the desired ReSeeD / docker host as described on the ["Transferring Images" page](/system/deployment/3_Transferring_Images).