Prebuilt docker image

[christian-herber-nxp]

Is your feature request related to a problem? Please describe.
I have a hard time spinning up the dev container, as I struggle to configure the docker container to work its way through all the proxies.
Specifically, all the apt-get command are failing.

Describe the solution you'd like
If a docker image existed, with everything needed to get started, that would enable me.

Describe alternatives you've considered
I did try configuring the proxy settings, but to no success.

[dhower-qc]

The docker image does exist: https://hub.docker.com/r/riscvintl/udb. The setup scripts should be trying to pull it down. Can you provide some more details about what was happening?

[christian-herber-nxp]

Thanks for that pointer, I guess this might help me somehow.
The devcontainer.json invokes a built of the docker image from the dockerfile:

"build": { "dockerfile": "Dockerfile" },

within the docker file, there are a bunch of apt-get commands. These are failing for me seemingly.
I am quite confident this is due to the corporate IT setup, with a zscaler proxy.

[christian-herber-nxp]

After digging through bin/setup, and really trying to see where things fail, it seems that it happens when additional packages are being pulled, e.g. python packages through pip or gems.
This is failing due to the missing proxy configuration.

best case, there could be a pre-built dev container, that just works and needs no additional installations after pulling the image.

[christian-herber-nxp]

I have made big progress getting at least the docker container somewhat working (without the devcontainer).
I had to edit the proxy configuration, so that it will even listen to the docker container, and had to pass the proxy address explicitly in setup like

DOCKER_BASE="docker run -v ${ROOT}:${ROOT} -w ${ROOT} -e http_proxy=$PROXY -e https_proxy=$PROXY riscvintl/udb:${CONTAINER_TAG}"

Like this, everything works in the container setup, with the exception of bundle install.
I cannot seem to direct bundle to the proxy, not even with:

    ${RUN} bundle config set --local http://rubygems.org $PROXY
    ${RUN} bundle config set --local https://rubygems.org $PROXY

Again, I wonder why it is even needed to do this all dynamically, and why these are not already contained in the image, like with riscvintl/riscv-docs-base-container-image.

[dhower-qc]

We decided to keep the libraries installed outside the container so that we didn't have to rebuild every time a library is added/changes. I'm happy to revisit this decision; it made more sense early in the project, but we may have reached a point where the tradeoffs have changed.

@kbroch-rivosinc, any opinion on this?

[7908837174]

Please assign this to me—happy to explore a proxy-resilient prebuilt container solution.