The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
This is a consequence of using Docker images. The .aderc file in your AutowareAuto repo specifies the list of Docker images to use when ade start is run. That portion of the file should look something like this:
export ADE_IMAGES=" registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master registry.gitlab.com/apexai/ade-atom:latest registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "When you run `ade start`, `ade` looks for those images in your Docker daemon (you can see what images you have already downloaded with the command `docker image ls`). When you run a Docker image, you're creating a container which is ephemeral. However, the changes you make to the container are not _lost_ when you shut it down (for example, with `ade stop`), they're just not easily visible. If you run `docker container ls` while `ade` is running, you should see something like the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES `ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Up 27 hours ade` `b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Up 27 hours ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master` `89fa0b5f53b1 registry.gitlab.com/apexai/ade-atom:latest "/bin/sh -c 'trap 'e…" 12 days ago Up 27 hours ade_registry.gitlab.com_apexai_ade-atom_latest`Now, if you run `ade stop`, the command `docker container ls` will show nothing because it only lists _running_ containers. However, if you add the `-a` (all) flag, you should get:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ef9dc36ee388 126c6aa92603 "/bin/sh -c 'apt-get…" 21 hours ago Exited (100) 21 hours ago flamboyant_carson ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Exited (147) 5 seconds ago ade b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Exited (147) 5 seconds ago ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master af22583e202a 1c1c55d72635 "gitlab-runner-helpe…" 2 days ago Exited (0) 2 days ago runner--project-0-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8 54ddde93b780 registry.gitlab.com/apexai/ade-lgsvl:2020.01 "/bin/sh -c 'trap 'e…" 6 days ago Exited (147) 5 seconds ago ade_registry.gitlab.com_apexai_ade-lgsvl_2020.01 ...
The formatting is a bit of a mess but you're looking for the image with the IMAGE name of registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master. This is the actual container that you made your changes in when running ade. You can then _save_ the changes you made to that container as a new image. In my example below, the _container_ that is running the ade _image_ is also named ade. To save that _container_ with the changes you made as a new _image_, you just have to commit it with a tag like this: docker commit ade my-repo:ade. Now, if you replace the first image entry in your .aderc (registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master) with your new image (my-repo:ade), when you run ade start, you'll enter into your new image.
Side note: If you want to save this image outside of your local Docker daemon, you should create a free DockerHub account then use docker login to log into it. After this, log onto DockerHub and create a new repo called my-repo and you'll be able to docker push your image to it.
| | 2 | No.2 Revision |
This is a consequence of using Docker images. The .aderc file in your AutowareAuto repo specifies the list of Docker images to use when ade start is run. That portion of the file should look something like this:
export ADE_IMAGES=" registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master registry.gitlab.com/apexai/ade-atom:latest registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:masterWhen you run""
ade start, ade looks for those images in your Docker daemon (you can see what images you have already downloaded with the command docker image ade stop), they're just not easily visible. If you run docker container ade is running, you should see something like the CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES `ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Up 27 hours ade` `b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Up 27 hours ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master` `89fa0b5f53b1 registry.gitlab.com/apexai/ade-atom:latest "/bin/sh -c 'trap 'e…" 12 days ago Up 27 hoursNow, if you runade_registry.gitlab.com_apexai_ade-atom_latest`ade_registry.gitlab.com_apexai_ade-atom_latest`
ade stop, the command docker container -a (all) flag, you should get: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ef9dc36ee388 126c6aa92603 "/bin/sh -c 'apt-get…" 21 hours ago Exited (100) 21 hours ago flamboyant_carson ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Exited (147) 5 seconds ago ade b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Exited (147) 5 seconds ago ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master af22583e202a 1c1c55d72635 "gitlab-runner-helpe…" 2 days ago Exited (0) 2 days ago runner--project-0-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8 54ddde93b780 registry.gitlab.com/apexai/ade-lgsvl:2020.01 "/bin/sh -c 'trap 'e…" 6 days ago Exited (147) 5 seconds ago ade_registry.gitlab.com_apexai_ade-lgsvl_2020.01 ...
The formatting is a bit of a mess but you're looking for the image with the IMAGE name of registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master. This is the actual container that you made your changes in when running ade. You can then _save_ the changes you made to that container as a new image. In my example below, the _container_ that is running the ade _image_ is also named ade. To save that _container_ with the changes you made as a new _image_, you just have to commit it with a tag like this: docker commit ade my-repo:ade. Now, if you replace the first image entry in your .aderc (registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master) with your new image (my-repo:ade), when you run ade start, you'll enter into your new image.
Side note: If you want to save this image outside of your local Docker daemon, you should create a free DockerHub account then use docker login to log into it. After this, log onto DockerHub and create a new repo called my-repo and you'll be able to docker push your image to it.
| | 3 | No.3 Revision |
This is a consequence of using Docker images. The .aderc file in your AutowareAuto repo specifies the list of Docker images to use when ade start is run. That portion of the file should look something like this:
export ADE_IMAGES=" registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master registry.gitlab.com/apexai/ade-atom:latest registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "
When you run ade start, ade looks for those images in your Docker daemon (you can see what images you have already downloaded with the command docker image ls). When you run a Docker image, you're creating a container which is ephemeral. However, the changes you make to the container are not _lost_ lost when you shut it down (for example, with ade stop), they're just not easily visible. If you run docker container ls while ade is running, you should see something like the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES `ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Up 27 hours ade` `b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Up 27 hours ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master` `89fa0b5f53b1 registry.gitlab.com/apexai/ade-atom:latest "/bin/sh -c 'trap 'e…" 12 days ago Up 27 hours ade_registry.gitlab.com_apexai_ade-atom_latest`
Now, if you run ade stop, the command docker container ls will show nothing because it only lists _running_ containers. However, if you add the -a (all) flag, you should get:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ef9dc36ee388 126c6aa92603 "/bin/sh -c 'apt-get…" 21 hours ago Exited (100) 21 hours ago flamboyant_carson ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Exited (147) 5 seconds ago ade b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Exited (147) 5 seconds ago ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master af22583e202a 1c1c55d72635 "gitlab-runner-helpe…" 2 days ago Exited (0) 2 days ago runner--project-0-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8 54ddde93b780 registry.gitlab.com/apexai/ade-lgsvl:2020.01 "/bin/sh -c 'trap 'e…" 6 days ago Exited (147) 5 seconds ago ade_registry.gitlab.com_apexai_ade-lgsvl_2020.01 ...
The formatting is a bit of a mess but you're looking for the image with the IMAGE name of registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master. This is the actual container that you made your changes in when running ade. You can then _save_ the changes you made to that container as a new image. In my example below, the _container_ that is running the ade _image_ image is also named ade. To save that _container_ container with the changes you made as a new _image_, image, you just have to commit it with a tag like this: docker commit ade my-repo:ade. Now, if you replace the first image entry in your .aderc (registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master) with your new image (my-repo:ade), when you run ade start, you'll enter into your new image.
Side note: If you want to save this image outside of your local Docker daemon, you should create a free DockerHub account then use docker login to log into it. After this, log onto DockerHub and create a new repo called my-repo and you'll be able to docker push your image to it.
| | 4 | No.4 Revision |
This is a consequence of using Docker images. The .aderc file in your AutowareAuto repo specifies the list of Docker images to use when ade start is run. That portion of the file should look something like this:
export ADE_IMAGES=" registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master registry.gitlab.com/apexai/ade-atom:latest registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "
When you run ade start, ade looks for those images in your Docker daemon (you can see what images you have already downloaded with the command docker image ls). When you run a Docker image, you're creating a container which is ephemeral. However, the changes you make to the container are not lost when you shut it down (for example, with ade stop), they're just not easily visible. If you run docker container ls while ade is running, you should see something like the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES `ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Up 27 hours ade` `b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Up 27 hours ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master` `89fa0b5f53b1 registry.gitlab.com/apexai/ade-atom:latest "/bin/sh -c 'trap 'e…" 12 days ago Up 27 hours ade_registry.gitlab.com_apexai_ade-atom_latest`
Now, if you run ade stop, the command docker container ls will show nothing because it only lists _running_ containers. However, if you add the -a (all) flag, you should get:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ef9dc36ee388 126c6aa92603 "/bin/sh -c 'apt-get…" 21 hours ago Exited (100) 21 hours ago flamboyant_carson ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Exited (147) 5 seconds ago ade b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Exited (147) 5 seconds ago ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master af22583e202a 1c1c55d72635 "gitlab-runner-helpe…" 2 days ago Exited (0) 2 days ago runner--project-0-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8 54ddde93b780 registry.gitlab.com/apexai/ade-lgsvl:2020.01 "/bin/sh -c 'trap 'e…" 6 days ago Exited (147) 5 seconds ago ade_registry.gitlab.com_apexai_ade-lgsvl_2020.01 ...
The formatting is a bit of a mess but you're looking for the image with the IMAGE name of registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master. This is the actual container that you made your changes in when running ade. You can then _save_ the changes you made to that container as a new image. In my example below, the _container_ that is running the ade image is also named ade. To save that container with the changes you made as a new image, you just have to commit it with a tag like this: docker commit ade . my-username/my-repo:ade (replacing my-repo:ademy-username with a username that you choose). Now, if you replace the first image entry in your .aderc (registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master) with your new image (my-repo:ademy-username/my-repo:adeade start, you'll enter into your new image.
Side note: If you want to save this image outside of your local Docker daemon, you should create a free DockerHub account then use docker login to log into it. After this, log onto DockerHub and create a new repo called my-repo and you'll be able to docker push your image to it.
| | 5 | No.5 Revision |
This is a consequence of using Docker images. The .aderc file in your AutowareAuto repo specifies the list of Docker images to use when ade start is run. That portion of the file should look something like this:
export ADE_IMAGES=" registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master registry.gitlab.com/apexai/ade-atom:latest registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "
When you run ade start, ade looks for those images in your Docker daemon (you can see what images you have already downloaded with the command docker image ls). When you run a Docker image, you're creating a container which is ephemeral. However, the changes you make to the container are not lost when you shut it down (for example, with ade stop), they're just not easily visible. If you run docker container ls while ade is running, you should see something like the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES `ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Up 27 hours ade` `b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Up 27 hours ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master` `89fa0b5f53b1 registry.gitlab.com/apexai/ade-atom:latest "/bin/sh -c 'trap 'e…" 12 days ago Up 27 hours ade_registry.gitlab.com_apexai_ade-atom_latest`
Now, if you run ade stop, the command docker container ls will show nothing because it only lists _running_ running containers. However, if you add the -a (all) flag, you should get:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ef9dc36ee388 126c6aa92603 "/bin/sh -c 'apt-get…" 21 hours ago Exited (100) 21 hours ago flamboyant_carson ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Exited (147) 5 seconds ago ade b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Exited (147) 5 seconds ago ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master af22583e202a 1c1c55d72635 "gitlab-runner-helpe…" 2 days ago Exited (0) 2 days ago runner--project-0-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8 54ddde93b780 registry.gitlab.com/apexai/ade-lgsvl:2020.01 "/bin/sh -c 'trap 'e…" 6 days ago Exited (147) 5 seconds ago ade_registry.gitlab.com_apexai_ade-lgsvl_2020.01 ...
The formatting is a bit of a mess but you're looking for the image with the IMAGE name of registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master. This is the actual container that you made your changes in when running ade. You can then _save_ the changes you made to that container as a new image. In my example below, the _container_ that is running the ade image is also named ade. To save that container with the changes you made as a new image, you just have to commit it with a tag like this: docker commit ade my-username/my-repo:ade (replacing my-username with a username that you choose). Now, if you replace the first image entry in your .aderc (registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master) with your new image (my-username/my-repo:ade), when you run ade start, you'll enter into your new image.
Side note: If you want to save this image outside of your local Docker daemon, you should create a free DockerHub account then use docker login to log into it. After this, log onto DockerHub and create a new repo called my-repo and you'll be able to docker push your image to it.
| | 6 | No.6 Revision |
This is a consequence of using Docker images. The .aderc file in your AutowareAuto repo specifies the list of Docker images to use when ade start is run. That portion of the file should look something like this:
export ADE_IMAGES=" registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master registry.gitlab.com/apexai/ade-atom:latest registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "
When you run ade start, ade looks for those images in your Docker daemon (you can see what images you have already downloaded with the command docker image ls). When you run a Docker image, you're creating a container which is ephemeral. However, the changes you make to the container are not lost when you shut it down (for example, with ade stop), they're just not easily visible. If you run docker container ls while ade is running, you should see something like the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES `ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Up 27 hours ade` `b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Up 27 hours ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master` `89fa0b5f53b1 registry.gitlab.com/apexai/ade-atom:latest "/bin/sh -c 'trap 'e…" 12 days ago Up 27 hours ade_registry.gitlab.com_apexai_ade-atom_latest`
Now, if you run ade stop, the command docker container ls will show nothing because it only lists running containers. However, if you add the -a (all) flag, you should get:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ef9dc36ee388 126c6aa92603 "/bin/sh -c 'apt-get…" 21 hours ago Exited (100) 21 hours ago flamboyant_carson ee3e44533985 registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master "/ade_entrypoint /bi…" 27 hours ago Exited (147) 5 seconds ago ade b7d35ddaacaf registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto:master "/bin/sh -c 'trap 'e…" 27 hours ago Exited (147) 5 seconds ago ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_master af22583e202a 1c1c55d72635 "gitlab-runner-helpe…" 2 days ago Exited (0) 2 days ago runner--project-0-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8 54ddde93b780 registry.gitlab.com/apexai/ade-lgsvl:2020.01 "/bin/sh -c 'trap 'e…" 6 days ago Exited (147) 5 seconds ago ade_registry.gitlab.com_apexai_ade-lgsvl_2020.01 ...
The formatting is a bit of a mess but you're looking for the image with the IMAGE name of registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master. This is the actual container that you made your changes in when running ade. You can then _save_ the changes you made to that container as a new image. In my example below, the _container_ that is running the ade image is also named ade. To save that container with the changes you made as a new image, you just have to commit it with a tag like this: docker commit ade my-username/my-repo:ade (replacing my-username with a username that you choose). Now, if you replace the first image entry in your .aderc (registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/ade:master) with your new image (my-username/my-repo:ade), when you run ade start, you'll enter into your new image.
Side note: If you want to save this image outside of your local Docker daemon, you should create a free DockerHub account with the username you used above then use docker login to log into it. After this, log onto DockerHub in a browser and create a new repo called my-repo and you'll be able to docker push your image to it.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.