indy-node-container
indy-node-container copied to clipboard
hyperledger
podman dependency in node controller
In https://github.com/hyperledger/indy-node-container/pull/107 I removed podman from the controller
- as a quick fix (apt install was failing and so did the lvl1 solution)
- why do we install podman into the container in the first place?
If we need podman, we need to solve the packacke dependency issues. TBD in our next call.
@tsurai @mgmgwi
Yes we do want to have podman, but actually only the CLI
- find a package (possibly on different base image) that does not depend on saystemd and install that one
- Simplest solution: fix old version
The original problem seems to have been resolved upstream and the package can be installed again. I've been unable to find a way to only install an remote API client and avoid the unneeded requirements.
@tsurai from https://podman.io/getting-started/installation#installing-on-linux
CAUTION: The Kubic repo is NOT recommended for production use.
-> do we need those? or can we use the version from the ubuntu repos? Maybe for some later ubuntu version?
Ok, I have tried quite a few base containers and eithere there is no python 3.5 or no podman available... lets stick with your ubuntu18 + kubic debs for now. ;)
decision as of 2022-10-14:
- Build an additional controller image without podman + "non prod" sources