Fork Autoware_AI repository and create docker image
Hi Autoware_AI currently does not include some vehicles that I wish to use to work with python API. I need to make some changes into the code, modify launch files, etc to make my simulation based on Autoware_AI repository https://github.com/Autoware-AI/docker...
It is not feasible change the code, let it inside shared_dir ( folder with access to my desktop and to the docker) and every time when I build the standard Autoware_AI image to remove and add the modified package code with my modifications.
For this reason I wish to fork the original github packages a little bit, and afterwards create an image based on my for and not based on the original repo.
As a solution to work on my codes I was trying to use a branch. However when I exit docker the branch does not exist anymore after issue the cmd below to use docker.
./run.sh -t 1.14.0
the image will build the standard docker image and the created branch no longer exist!
Wha would be the best option do be done? And where can I find a good tutorial for this case involving fork Autoware project?
Thanks in advance!
---------------------------------------------------------------------------------------------------------------------------------------------------------------As solution I tried 2 different approaches:
ATTEMPT 1:
1) To modify the container and save it as described here: https://www.scalyr.com/blog/create-do...
Then using other terminal, trying to add .txt file for Autoware_AI running container, to modify the container, Autoware_AI container does not appear as active (but it is). Just other container are avaialable when I try to copy a file to Autoware_AI:
$ docker cp file.txt (Twice tab): ade: ade_registry.gitlab.com_autowarefoundation_autoware.auto_ade-lgsvl_foxy_2020.06: ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_amd64_ade-foxy_master: ade_registry.gitlab.com_autowarefoundation_autoware.auto_autowareauto_amd64_binary-foxy_master: hi_mom:
These ade images above are from AutowareAuto, not from AutowareAI, that I wish to use. I have just as external option to access Autoware.Auto images path and the nginx(Hi mom) image (from this tutorial link passed). Unfortunately docker command does not work inside the running container terminal…
But if I list the images I have available, it is possible to see that AutowareAI image was built:
$ docker images:
REPOSITORY TAG IMAGE ID CREATED SIZE
ubuntu latest 26b77e58432b 2 weeks ago 72.9MB
autoware/autoware local-melodic-cuda 4997df3ad6dc 2 weeks ago 10.3GB
autoware/autoware local-melodic-base-cuda 8fb0b62fcab2 2 weeks ago 6.99GB
autoware/autoware local-melodic-base 0d87fce181db 2 weeks ago 3.45GB
registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/amd64/binary-foxy master 46ac7d2cbd73 2 weeks ago 144MB
registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/amd64/ade-foxy master acd13c509891 3 weeks ago 4.59GB
lgsvl/simulator-scenarios-runner simulator-build__2021.1 63c9bdef5e3a 5 weeks ago 413MB
registry.gitlab.com/autowarefoundation/autoware.auto/autowareauto/amd64/ade-foxy <none> 6448c91f68e8 6 weeks ago 4.85GB
registry.gitlab.com/autowarefoundation/autoware.auto/ade-lgsvl/foxy 2020.06 7be8da9ce3bb 2 months ago 251MB
etc...
However you can check in right upper terminal or in left bottom terminal the Autoware_AI container is running with the name ( autoware/autoware: 1.14.0-melodic-cuda). Different from AutowareAuto project that ...