Not necessarily installation of libindy_vdr.so and ibaries_askar.so into $HOME/.local/lib

[vitalrev]

In next Dockerfile...

indy-vdr python wrapper already contains the cargo library libindy_vdr.so, see snippet:
cp target/*/libindy_vdr.so wrappers/python/indy_vdr && \

So, the copy to $HOME/.local/lib is not necessary:
cp target/*/libindy_vdr.so "$HOME/.local/lib" && \

The whole snippet:

# Build and install indy-vdr
# Ensure libindy_vdr.so is included in the python package to avoid 'Library not loaded from python package' messages.
WORKDIR $HOME/indy-vdr
RUN cd indy-vdr* && \
    cargo build ${indy_build_flags} && \
    cp target/*/libindy_vdr.so "$HOME/.local/lib" && \
    cp target/*/libindy_vdr.so wrappers/python/indy_vdr && \
    cp target/*/indy-vdr-proxy "$HOME/.local/bin" && \
    cargo clean

I tested it:
created a new docker image based on von-image:next-2 and removed the libindy_vdr.so from $HOME/.local/lib
RUN rm -rf /home/indy/.local/lib/libindy_vdr.so
and, indy-vdr works fine (in context of tails-server), see pull request in tails-server bcgov/indy-tails-server#38

I think, the same for ibindy_credx.so and libaries_askar.so, this cargo libraries are also parts of python wrappers