Conda environment activation at startup - Singularity about trained-models

[satra]

@gaiborjosue - take a look at this section: https://apptainer.org/docs/user/latest/docker_and_oci.html#cmd-entrypoint-behaviour

i'll try to create a simple miniconda/mamba container with multiple environments to see whether i can support this.

yes, to build singularity you have to be root, or you can use a docker apptainer container in privileged mode to build the recipe

[gaiborjosue]

I will take a look at that right now. Thank you for the resource.

[gaiborjosue]

Hello @satra, I was just wondering if your container testing supports the multi environment activation. I tested with cmd and entrypoint but it still does not work for me. Thank you!

[satra]

just like this example from the link above:

# CMD="date"

# Runs 'date'
$ apptainer run mycontainer.sif
Wed 06 Oct 2021 02:45:39 PM CDT

# Runs 'echo hello'
$ apptainer run mycontainer.sif echo hello
hello

can't you simply do:

$ apptainer run mycontainer.sif /path/to/conda/env/bin/python ...

[hvgazula]

requires knowing the environment name ahead of time..meaning we either have to parse the file for the name or activate an environment that is not base. I still think..standardizing it by installing in base environment is easy and maintainable.

[hvgazula]

I guess I am addressing a different issue 😄 . I will let @gaiborjosue respond first.

[gaiborjosue]

Hello, I agree with Harsha. That would require us having to parse the conda env name somehow.

[satra]

supports the multi environment activation

i thought your question was about multiple environments, not a single environment. a single environment can be made default with CMD or ENTRYPOINT as demonstrated in the examples on apptainer.

another way of controlling environments is to modify the default environment in which a script is executed through controlling shebang #! . this can be done through a fit.sh or predict.sh script that wraps the python or other script the model provides. if the script wants different environments that's part of the ingest of script process. if it's simply a default environment then that can always be included in the CMD/ENTRYPOINT.

[gaiborjosue]

@satra Thanks for the response. Yes, my question derivated from the suggestion of allowing users to have multiple environments for their model's dockerfile. Just in case they have different use-cases for the same model. However, in the current structure, cli does not activate a specific environment (other than base) automatically. Therefore, the problem was that we don't have any way of knowing which environment the user wants to activate for that specific use case scenario.

fit.sh or predict.sh

Also, per my understanding, cli when building the image, can't/does not run any .sh file. Therefore, the ideal thing would be to do it everything inside the Dockerfile. Is this possible?

[satra]

cli when building the image

the cli doesn't build an image right, it uses the image built from the dockerfile. so if the dockerfile has a few commands added that creates a startup script that can use appropriate environments in the image that should be fine.

1. a docker image is essentially an OS, it can have many environments in it, including different conda environments.
2. when calling a script inside the instance of that image, one can both initialize and refer to any of those environments.

it may be useful to write down the exact sets of commands of what it is you are trying to do with a specific image and we can work through that together. all of this should simply be a manipulation of scripts and entrypoints.

[hvgazula]

@gaiborjosue I guess this is resolved as well. Isn't it?

[gaiborjosue]

@hvgazula Right now, we are using base env at startup. Will work on this again, sorry if I have put this issue on hold.

[hvgazula]

See here for why singularity image cannot activate the conda environment on entry.

[satra]

See here for why singularity image cannot activate the conda environment on entry.

most of that response is about layer reduction, which is irrelevant to the notion of conda environment activation. the only two instruction types that are relevant are CMD and ENTRYPOINT.

please see my comments here on how to achieve this: #75 (comment) (or discuss why that cannot be implemented).