Docker Build Issues with Trame and Wslink

[ferracioli]

Hi everyone,

Our company team uses a Trame-based image to build a Docker container for our dashboard. Recently, the build process for new versions of this image has stopped working. Below are the important points we've observed. Can anyone advise on how to resolve these issues and get the image build working again?

• Wslink released version 2.0.0 recently
• Since 29/05(after the wslink new release), our build is returning this message even when starting the build from scratch:
  Error while finding module specification for 'wslink.launcher' (ModuleNotFoundError: No module named 'wslink')
• We are using this trame image: kitware/trame:1.2-glvnd-runtime-ubuntu20.04-py39, but even in recently updated images from Docker hub it does not work
• It seems the build_server.sh script is not creating the expected folder(empty files and subfolders such logs)
• The suggestion in the link below does not work in our case, since we already are using a proper trame image:
  https://discourse.vtk.org/t/docker/11106

[jourdain]

So the new image set to use should be kitware/trame:py3.9-glvnd.
We stop generating the names you are using 6 months ago.

You can see the available tags here

[jourdain]

Your are giving me the output of docker running, not the output of the docker building.

Maybe you can do RUN /opt/trame/entrypoint.sh build &> /deploy/server/build-step.txt

And post the content of that file? (I mean /deploy/server/build-step.txt from within the docker)

[ferracioli]

Sorry for the delay, when we try to check the error log, the build-step.txt file always stores a message telling the installed libraries. The only exception is the part
ERROR: Invalid requirement: '/local-app' Hint: It looks like a path. File '/local-app' does not exist.
It seems that this local-app was build during the build_server.sh script, which was skipped(build_server script shown in the bottom of the answer).

Besides that, we always end up with the previous error message, even when including the wslink in the requirements.

#!/usr/bin/env bash
CURRENT_DIR=`dirname "$0"`

# Since Mac doesn't come with realpath by default, let's set the full
# paths using PWD.
pushd .
cd $CURRENT_DIR/..
DEPLOY_DIR=$PWD
cd $CURRENT_DIR/../../..
ROOT_DIR=$PWD
popd

echo $CURRENT_DIR
echo $DEPLOY_DIR
echo $ROOT_DIR

 docker run           \
     -e TRAME_BUILD_ONLY=1 \
     -v "$DEPLOY_DIR:/deploy" \
     -v "$ROOT_DIR:/local-app" \
     kitware/trame:py3.9-glvnd

[jourdain]

It seems pretty obvious that you probably skipped copying your app into /local-app within docker.

[jourdain]

I mean ideally you should understand what each step is doing but the main goal is to install your project with its dependecies into the virtual environment within docker.

So here, you try to install /local-app into the venv but nothing is there...

[ferracioli]

We managed to fix the problem after a lot of searching. Due to some updates in the Trame repository, our build method became deprecated, which was causing the build_server.sh script to stop working properly. We followed the changes made in this commit to resolve the issue: Kitware/trame-cookiecutter@4e8dcd8

Thank you for your attention and suggestions to help us fix our Dashboard, Jourdain :)