You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When pulling the images from ghrc.io there is no specification for the role of the different FEDn containers I am trying to deploy (api-server, combiner, client etc). Particularly for a combiner container I want to pull and create since they rely on the build arg/env variable GRPC_HEALTH_PROBE_VERSION to run successfully. Doing this might let us cut down the container size even more too.
Describe the solution you'd like
Add entries in the build_containers.yaml workflow so that I can specify the correct role for my container (that has been built with the correct build args)
OR
Having the single fedn container on be able to wear any hat in the system and work out of the box.
How would the solution positively affect the functionality?
Running the listed container(s) without additional build steps is more convenient.
Describe any drawbacks (if any)
Confusion if you just are trying to run clients and don't know what a combiner or api-server is. And it's more containers to manage/support in the git flow pipeline
Is your feature request related to a problem? Please describe.
When pulling the images from ghrc.io there is no specification for the role of the different FEDn containers I am trying to deploy (api-server, combiner, client etc). Particularly for a combiner container I want to pull and create since they rely on the build arg/env variable GRPC_HEALTH_PROBE_VERSION to run successfully. Doing this might let us cut down the container size even more too.
Describe the solution you'd like
Add entries in the build_containers.yaml workflow so that I can specify the correct role for my container (that has been built with the correct build args)
OR
Having the single fedn container on be able to wear any hat in the system and work out of the box.
How would the solution positively affect the functionality?
Running the listed container(s) without additional build steps is more convenient.
Describe any drawbacks (if any)
Confusion if you just are trying to run clients and don't know what a combiner or api-server is. And it's more containers to manage/support in the git flow pipeline
Contact Details
[email protected]
The text was updated successfully, but these errors were encountered: