voxl-cross docker image without network

[Nicholas Clark]

On a system without direct access to the internet, the voxl-cross docker image version 2.7 executes this scipt when a login shell is created which triggers multiple http requests that will not complete on an offline system:

/etc/profile.d/local_completions.sh

AVAILABLE_SECTIONS=( "$(wget http://voxl-packages.modalai.com/dists/qrb5165 -q -
O- | grep ' -' | cut -d '>' -f 2 | cut -d '/' -f 1 )" )

AVAILABLE_DISTS=( "$( wget http://voxl-packages.modalai.com/dists -q -O- | grep
' -' | cut -d '>' -f 2 | cut -d '/' -f 1 )" )

The voxl-docker wrapper script has this as its default entrypoint:

ENTRYPOINT="/bin/bash -l" # login shell so it loads /etc/profile

The combination of the default entrypoint requiring a login shell and the voxl-cross containing mandatory network calls as part of the login process lead to an unstable image.

[Moderator]

@Nicholas-Clark you can find the voxl-cross Dockerfile and source here. We're happy to incorporate merge requests if you feel you have a solution that can be generalized across our customers.