A while back a dsub user asked the question whether or not it was possible to use a custom boot image. The answer then was 'no'. I know there have been a lot of recent developments in the pipeline API, and there's an attribute in the latest API for specifying a bootImage for the run method. It says its restricted to Container-Optimized OS images, which of course makes sense. Does anyone know if you can use this with a custom image, say one made from the default OS image used? I've got an inquiry in the life sciences google group to see if one can use this attribute to use a custom image. If so I'd love to see/add an bootImage option to dsub.
Why would we want to do this? Good question. We're using dsub in a health care environment and our information security group is requiring us to have one or more client agents installed on all virtual machines. Because the nature of our dsub jobs take > 12 hrs, they're not receptive to altering this policy for even "shortish" tasks.
A while back a dsub user asked the question whether or not it was possible to use a custom boot image. The answer then was 'no'. I know there have been a lot of recent developments in the pipeline API, and there's an attribute in the latest API for specifying a bootImage for the run method. It says its restricted to Container-Optimized OS images, which of course makes sense. Does anyone know if you can use this with a custom image, say one made from the default OS image used? I've got an inquiry in the life sciences google group to see if one can use this attribute to use a custom image. If so I'd love to see/add an bootImage option to dsub.
Why would we want to do this? Good question. We're using dsub in a health care environment and our information security group is requiring us to have one or more client agents installed on all virtual machines. Because the nature of our dsub jobs take > 12 hrs, they're not receptive to altering this policy for even "shortish" tasks.