Arvados

So if the problem is mainly using /tmp, we should be using a different directory, maybe /root or /var/spool/something ?

Yes, I was thinking in just using $HOME/tmp for every case. Maybe a-d-c would benefit of a new config knob to set that directory to some sensible (or /tmp) default?

TODO split this into 3 tickets.

21999-packer-fixes @ 72d634e3cf

packer-build-compute-image: #260

• All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
  • Yes
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • This story doesn't explicitly mention that the packer scripts should work with a CIS L1 AMI (ami-0dc4762eb2bdd9a25). I've done some manual testing and it fails on the singularity build stage, unrelated to running things in /tmp.
• Code is tested and passing, both automated and manual, what manual testing was done is described.
  • I've manually tested creating an AMI passing --workdir /home/admin and it worked fine.
• New or changed UX/UX and has gotten feedback from stakeholders.
  • Just a new --workdir <path> argument
• Documentation has been updated.
  • Yes
• Behaves appropriately at the intended scale (describe intended scale).
  • N/A
• Considered backwards and forwards compatibility issues between client and server.
  • Yes. The working directory is now parametrized, and defaults to /tmp so it's backwards compatible.
• Follows our coding standards and GUI style guidelines.
  • N/A

Because this story is about being able to support base images with /tmp mounted with noexec, I made it possible for the user to specify another path instead of /tmp.
Additional work is required to make it work with CIS Level 1 Debian 11, because for some reason when trying to build singularity it doesn't detect the Go compiler (although there's no error output related to the Go compiler installation phase):

...
    amazon-ebs: Processing triggers for libc-bin (2.31-13+deb11u11) ...
    amazon-ebs: Configuring for project `singularity-ce' with languages: C, Golang
    amazon-ebs: => running pre-basechecks project specific checks ...
    amazon-ebs: => running base system checks ...
    amazon-ebs:  checking: host C compiler... cc
    amazon-ebs:  checking: host C++ compiler... c++
    amazon-ebs:  checking: host Go compiler (at least version 1.17)... not found!
    amazon-ebs: mconfig: could not complete configuration
==> amazon-ebs: Provisioning step had errors: Running the cleanup provisioner, if present...
==> amazon-ebs: Terminating the source AWS instance...
==> amazon-ebs: Cleaning up any extra volumes...
==> amazon-ebs: No volumes to clean up, skipping
==> amazon-ebs: Deleting temporary security group...
==> amazon-ebs: Deleting temporary keypair...
Build 'amazon-ebs' errored after 6 minutes 7 seconds: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]

Lucas Di Pentima wrote in #note-15:

21999-packer-fixes @ 72d634e3cf

Just one --workdir documentation nit: in the phrase "The directory on which," using the preposition "on" to describe stuff that happens "in" the directory sounds just slightly off to native English speaker ears. Suggest instead:

The directory where data files are staged and setup scripts are run

If you want to workshop it further in chat, happy to do that. Please go ahead and merge, thanks.

Thanks for the suggestion, fixed and merged!