Skip to content

Commit 5f3ac57

Browse files
committed
Rename stage in apt get example
while keeping with uniquely spelled noun that is self descriptive yet unmistakable
1 parent ebf1820 commit 5f3ac57

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

ros/content.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ The Robot Operating System (ROS) is a set of software libraries and tools that h
1313
To create your own ROS docker images and install custom packages, here's a simple example of installing the C++, Python client library demos using the official released Debian packages via apt-get.
1414

1515
```dockerfile
16-
FROM %%IMAGE%%:rolling-ros-core as installer
16+
FROM %%IMAGE%%:rolling-ros-core as aptgetter
1717

1818
# install ros package
1919
RUN apt-get update && apt-get install -y \
@@ -28,8 +28,8 @@ CMD ["ros2", "launch", "demo_nodes_cpp", "talker_listener_launch.py"]
2828
Note: all ROS images include a default entrypoint that sources the ROS environment setup before executing the configured command, in this case the demo packages launch file. You can then build and run the Docker image like so:
2929

3030
```console
31-
$ docker build -t my/ros:installer .
32-
$ docker run -it --rm my/ros:installer
31+
$ docker build -t my/ros:aptgetter .
32+
$ docker run -it --rm my/ros:aptgetter
3333
[INFO] [launch]: process[talker-1]: started with pid [813]
3434
[INFO] [launch]: process[listener-2]: started with pid [814]
3535
[INFO] [talker]: Publishing: 'Hello World: 1'
@@ -146,12 +146,12 @@ The example above consists of three sequential stages. The `cacher` stage first
146146
- Builds and installs only a select few packages in the workspace
147147
- Only workspace install artifacts are copied into final layers
148148

149-
For comparison, the resulting `runner` image is similar in size to the earlier `installer` example. This allows you to develop and distribute custom ROS packages without significantly increasing image size compared to pre-built Debian installations:
149+
For comparison, the resulting `runner` image is similar in size to the earlier `aptgetter` example. This allows you to develop and distribute custom ROS packages without significantly increasing image size compared to pre-built Debian installations:
150150

151151
```console
152152
$ docker image ls my/ros --format "table {{.Tag}}\t{{.Size}}"
153153
TAG SIZE
154-
installer 504MB
154+
aptgetter 504MB
155155
runner 510MB
156156
builder 941MB
157157
$ docker image ls ros --format "table {{.Tag}}\t{{.Size}}"

0 commit comments

Comments
 (0)