"WSL distro proxy in Ubuntu distro has exited with an error: exit status 9" error

Image Builds
,
1

I have been trying to build an image in docker for an university project for several weeks now but I get a pop-up window from docker-desktop where this error is displayed and the build is stopped. Then it doesn’t let me continue and I have to restart the computer, restarting again from the beginning.

The command I use is $ docker build --build-arg git_user=my_user --build-arg git_token=my_token -t eye_control .

Where my_user and my_token are a github user and a github token.

I have never worked with docker and I really don’t know what could be the error causing this, so I would appreciate any help.

Thanks.

2

Unless you start sharing the content of the Dockerfile and the exact error message (and the lines above), there is nothing to work with.

3

The content of my dockerfile is the next:

FROM osrf/ros:noetic-desktop-focal

SHELL ["/bin/bash", "-c"] 

# install ros packages
RUN apt-get update && apt-get install -y --no-install-recommends \
    ros-noetic-desktop-full=1.5.0-1* \
    && rm -rf /var/lib/apt/lists/*

ARG DEBIAN_FRONTEND=noninteractive 

ARG use_gpu=True

RUN  apt-get update \
  && apt-get install -y wget \
  && apt-get install -y tree

##########################################
##########################################
# INSTALL OpenSim. 
# Use script from: https://github.com/opensim-org/opensim-core/tree/main/scripts/build
##########################################
RUN mkdir -p /home/user/opensim_installation
COPY opensim-core-linux-build-script.sh /home/user/opensim_installation/
RUN cd /home/user/opensim_installation && \
	chmod +x opensim-core-linux-build-script.sh && \
	./opensim-core-linux-build-script.sh -dRelWithDebInfo -copensim_451

RUN apt-get install python-is-python3
RUN apt-get install -y python3-pip

# Install OpenSim Python bindings: https://opensimconfluence.atlassian.net/wiki/spaces/OpenSim/pages/53085346/Scripting+in+Python
RUN cd ~/opensim-core/sdk/Python && \
	python3 -m pip install .
RUN echo 'export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/opensim-core/sdk/lib' >> ~/.bashrc 
RUN echo 'export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/opensim-core/sdk/Simbody/lib' >> ~/.bashrc

##########################################
##########################################

And the error of docker-desktop is the image that i have uploaded.

Ventana emergente docker desktop
Ventana emergente docker desktop1447×862 34 KB

thanks ans tell me if you need more info.
.

4

Can you identify which step stops the build?

I would try to install the app in a WSL2 distribution to see if WSL fails even without Docker Desktop or it is related to Docker Destkop.

And make sure you have enough resources available.

This issue on StackOverflow for example indicates memory problem

5

Thanks for your input. In principle, it fails me when I try to install OpenSim, I don’t know exactly where because the terminal gets stuck when the installation takes a while.

About the memory, I have 16 Gb of RAM and almost 1 Tb of hard disk available, so I guess I shouldn’t have problems there, although I don’t know if there is any way to check exactly if it crashes because of that.

Then, when you tell me to try to install the app in the WSL, it is not installing the docker image but the OpenSim application from Ubuntu?

6

If that is the RAM of the host, WSL2 has only 8GB. If you run other processes as well and the build requires lots of memory in addition to what Docker components are already using, it might not be enough.
But that is why I recommend installing the app without Docker, but in WSL2, so you have the same kernel, same memory limit, except you are not in a container. If it fails, it is either a RAM issue and you can try to increase that as described on StackOverlow (which lpoints to the official documentation from Microsoft) or it is something related to WSLs kernel, in which case you would need to ask the question on a Microsoft forum. If there is no problem without Docker in WSL2, it is likely a Docker desktop or Docker CE issue and we can continue trying to investigate.

Yes, but the same way as you tried with Docker, using the same commands..

7

Thank you very much for your help, I will try the indications you have given me and I will comment if the problem is fixed or not.