How to modify startup script which is executed on VMs after launching

[uray10]

Less of an issue. More of a question.

How can I modify the startup script that executes on the VMs after launching the instances using dsub? I want to modify the amount of memory available to the docker container and I can do that by controlling the --memory flag when doing a "docker run". I assume the docker run is being done by the startup script and that's why I want to know how to modify it.

[mbookman]

Hi @uray10 !

Can you explain in more detail why you want to modify the amount of memory used for a particular container? What is the problem you are looking to solve?

I don't think that the Pipelines API sets an explicit memory value on any of the containers it runs. Each container has access to all memory available on the VM.

Are you looking to just change either the --machine-type or --min-ram value?

BTW, the Pipelines API does not allow for passing a startup script for the VM.

[uray10]

I'm actually looking to vary the amount of memory available to a container and see how it affects the performance of an application. I can do that interactively by spinning up a VM and running docker on it, but I was wondering whether there was a way to do it via dsub

[mbookman]

If you use the the local provider, you could do some experimenting there:

https://github.com/DataBiosphere/dsub/blob/d4925d9e294b05a49fc93347f07010de137684f8/dsub/providers/local/runner.sh#L265