bcgov / von-image Goto Github PK

Test Comment

This PR was added to Indy Tails Server, but should be applied to this repo. Please update this repo to include these dependencies.

Automate the build process and produce multi-architecture images that support linux/amd64 and linux/arm64 (Apple M1 Friendly) architectures natively. Work needs to start here so we have a multi-architecture base image to use for bcgov/aries-cloudagent-container#42

Incorporate the changes from this PR; #27

Include indy-sdk cli in the base image so it is available to images that build on von-image.

bcgov/von-network#30

This issue is a kind reminder that your repository has been inactive for 361 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

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

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)