Closed armish closed 7 years ago
@armish did you test it?
gcloud
tends to also write in its installation directory (at least when automaticatlly getting new components); so if to users manipulate the same installation in /opt
I think we can run into access rights problems.
@smondet: nope - I haven't tested it yet. Was just curious what you think about this or whether this will break anything that is not obvious to me at the first place.
What would be a good way to fully test this, btw? Spin up a secobox using this branch and setting the Docker images to the corresponding ones?
Also relevant to this: #30
Currently, It is a bit hard to keep track of which image assumes which user and hence where the gcloud utils get installed. I had this issue while thinking about a workflow product that makes use of
gsutil
and realized thathammerlab/keredofi:coclobas-gke-biokepi-default
had gcloud utils installed only for theopam
user and ketrew was running as thebiokepi
. Since it would be ugly to try to call the utils from a different user's directory, I thought changing the path for the gcloud-sdk installation will give us some uniformity across images and apps.This is, of course, open to comments and other suggestions.