Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .env
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ PROJECT_NAME="airstack"
# If you've run ./airstack.sh setup, then this will auto-generate from the git commit hash every time a change is made
# to a Dockerfile or docker-compose.yaml file. Otherwise this can also be set explicitly to make a release version.
# auto-generated from git commit hash
VERSION="0.20.4"
VERSION="0.20.5"
# Image-tag discriminator ONLY (appears in the image tag suffix, e.g. ..._robot-x86-64_dev).
# No Dockerfile consumes it: "prebuilt" does NOT bake the built ros_ws into the image today —
# a real prebuilt (workspace-baked) stage is future work. Keep "dev" (mounted code, built live).
Expand Down
7 changes: 3 additions & 4 deletions docs/development/beginner/airstack-cli/docker_usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,20 +22,19 @@ docker compose build # Build from scratch

## Pull Images

To use the AirLab docker registry:
The AirLab docker registry (`airlab-docker.andrew.cmu.edu`) is public — no `docker login` is needed to pull:

```bash
cd AirStack/
docker login airlab-docker.andrew.cmu.edu
## <Enter your andrew id (without @andrew.cmu.edu)>
## <Enter your andrew password>

## Pull the images in the docker compose file
docker compose pull
```

The available image tags are listed [here](https://airlab-docker.andrew.cmu.edu/harbor/projects/2/repositories/airstack/artifacts-tab).

Pushing images still requires an AirLab account (`docker login airlab-docker.andrew.cmu.edu` first).

## Build Images

For an overview of build-time options (`BASE_IMAGE`, `ROS_DISTRO`, platform profiles), see [Docker Build Profiles](../../intermediate/docker-build-profiles.md). For runtime container operations, continue below.
Expand Down
10 changes: 4 additions & 6 deletions docs/getting_started/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
We'd really appreciate your feedback and contributions to improve this project for everyone!
Please join our #airstack channel on Slack to contribute or ask questions.

You will need to have an account with AirLab to access the AirLab Docker registry, Nucleus server, and other resources.
The AirLab Docker registry is public, so anyone can pull the Docker images without an account. You will need an account with AirLab to push images and to access the Nucleus server and other internal resources.
The API and functionality are not stable and are subject to change.


Expand Down Expand Up @@ -49,13 +49,10 @@ source ~/.bashrc # OR ~/.zshrc. applies settings to enable `airstack` command
Now you have two options on how to proceed. You can build the docker image from scratch or pull the existing image on the airlab docker registry. Building the image from scratch can be useful if you would like to add new dependencies or add new custom functionality. For most users just pulling the existing image will be more conveninent and fast since it doesn't require access to the Nvidia registry.

<details open> <summary>Option 1: Pull From the Airlab Docker Registry (Preferred)</summary>
To use the AirLab Docker registry do the following
The AirLab Docker registry (<code>airlab-docker.andrew.cmu.edu</code>) is public — no account or <code>docker login</code> is needed to pull.

```bash
cd AirStack/
docker login airlab-docker.andrew.cmu.edu
## <Enter your andrew id (without @andrew.cmu.edu)>
## <Enter your andrew password>

## Pull the images in the docker compose file
airstack images pull
Expand All @@ -76,9 +73,10 @@ The images will be pulled from the server automatically. This might take a while
airstack images build
```

If you have permission you can push updated images to the docker server.
If you have permission you can push updated images to the docker server. Pushing (unlike pulling) requires logging in with your AirLab account first.

```bash
docker login airlab-docker.andrew.cmu.edu
airstack images push
```

Expand Down
5 changes: 1 addition & 4 deletions docs/simulation/isaac_sim/container_workflows.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,10 +197,7 @@ ls $HOME/docker/isaac-sim/logs/
### Pulling Pre-built Images

```bash
# Login to AirLab registry
docker login airlab-docker.andrew.cmu.edu

# Pull Isaac Sim image
# Pull Isaac Sim image (the AirLab registry is public — no login needed)
docker compose -f simulation/isaac-sim/docker/docker-compose.yaml pull
```

Expand Down
5 changes: 1 addition & 4 deletions docs/simulation/ms-airsim/docker.md
Original file line number Diff line number Diff line change
Expand Up @@ -239,10 +239,7 @@ airstack up --sim airsim --robots 3
### Pulling Pre-built Images

```bash
# Login to AirLab registry
docker login airlab-docker.andrew.cmu.edu

# Pull image
# Pull image (the AirLab registry is public — no login needed)
docker compose -f simulation/ms-airsim/docker/docker-compose.yaml pull
```

Expand Down
Loading