ModuleNotFoundError

I’m running blender 2.80 from docker like this:

#!/bin/sh
exec \
  docker run -t \
  -e ADDON_DIRECTORIES_TO_LOAD \
  -e EDITOR_PORT \
  -e ALLOW_MODIFY_EXTERNAL_PYTHON \
  -e DISPLAY \
  -v /tmp/.X11-unix:/tmp/.X11-unix \
  -v /home/radivarig/:/home/radivarig \
  --network="host" \
  --device /dev/snd \
  ubuntu/blender:version3 \
  ./home/radivarig/projects/blender-env/blender-2.80-4dd0a90f4213-linux-glibc224-x86_64/blender "$@" \

I select it as blender executable after running Blender: Start, blender does opens but throws:

File "/home/radivarig/projects/blender-env/blender-2.80-4dd0a90f4213-linux-glibc224-x86_64/2.80/scripts/modules/addon_utils.py", line 351, in enable
    mod = __import__(module_name)
ModuleNotFoundError: No module named 'TestAddon'

The addon symlink is created under '/root/.config/blender/2.80/scripts/addons' inside the docker container and when I reset to factory settings or open blender by hand enabling the addon does work.

Any ideas?

[jessey-git]

It’s probably not related to docker. I’ve seen this happen as well on raw win10. For me it happened because I started with a completely blank Blender config directory and attempted to launch blender with my addon right away from vscode. To fix this I had to launch blender by itself first, and then enable my addon manually.

After that I was able to use the vscode extension normally. It seems that the extension has trouble if the addon doesn’t exist yet?

[Radivarig]

@jessey-git could you publish an update to the vscode market?