You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anomaly report (something appears to not work correctly)
Enhancement request (describe the enhancement being requested)
Other (please ensure the description clarifies why the issue doesn’t fall into either of the above categories)
Descriptive summary
When the CARMA repos underwent renaming the names of the forked 3rd party repos were reverted to their original names. I addition, the docker build scripts were modified such that the image name would use the repo name directly. Unfortunately, this cause a break between current images built on develop and images on dockerhub. This occurs for both the avt_vimba_camera repo and novatel_gps_driver repository. This means two switch between old and new image versions the user must change both the image name and version number. Additionally, since the new images are not associated with a dockerhub repository they must be built manually.
Probably best to revert the build script changes to ensure binaries are named as expected.
Expected behavior
Newest version of docker images can be used simply by controlling the version number and organization.
Software version this applies to
develop after 3.3.0
Actual behavior
Newest 3rd party forked repo images cannot be pushed to docker hub
Steps to reproduce the behavior
./build-image.sh -d on avt or novatel repo and observe image tag name.
Related work
Link to related tickets or prior related work here.
The text was updated successfully, but these errors were encountered:
Types of Issue
Descriptive summary
When the CARMA repos underwent renaming the names of the forked 3rd party repos were reverted to their original names. I addition, the docker build scripts were modified such that the image name would use the repo name directly. Unfortunately, this cause a break between current images built on develop and images on dockerhub. This occurs for both the avt_vimba_camera repo and novatel_gps_driver repository. This means two switch between old and new image versions the user must change both the image name and version number. Additionally, since the new images are not associated with a dockerhub repository they must be built manually.
Probably best to revert the build script changes to ensure binaries are named as expected.
Expected behavior
Newest version of docker images can be used simply by controlling the version number and organization.
Software version this applies to
develop after 3.3.0
Actual behavior
Newest 3rd party forked repo images cannot be pushed to docker hub
Steps to reproduce the behavior
./build-image.sh -d on avt or novatel repo and observe image tag name.
Related work
Link to related tickets or prior related work here.
The text was updated successfully, but these errors were encountered: