Open shonfeder opened 3 months ago
I hit this running local, but I expect the same behavior would happen running the main service.
This is less of a concern for the main service as we are deploying with Docker. We need to persist /capnp-secrets
so it will be mounted as a Docker volume. This will cause Docker to create the mount point/directory for us.
I hit this running
local
, but I expect the same behavior would happen running the main service. IMO, the best behavior would be to create the needed directory if doesn't already exist: this will make set up and deployment simpler, but at least, it should handle the error and report the issue correctly.(This is easy to fix, but I'm opening an issue so as not to pollute unrelated work with this fix.)
This is probably the place where the logic should be fixed: https://github.com/ocurrent/opam-repo-ci/blob/b11b27c68993bd1725e6202fe2b56a036d537610/service/capnp_setup.ml#L10-L25