0c71fc9d1d
In the spirit of Marie Kondo, I'm tidying up! TL;DR: - Prefer .envrc `use_nix` and delete all dir-locals.nix files - Remove ~all references to <nixpkgs>, <unstable>, <depot> and prefer referencing each with briefcase.third_party.{pkgs,unstable,depot} - Delete nixBufferFromShell function since I was only using that in dir-locals.nix files |
||
---|---|---|
.. | ||
cloud_run.nix | ||
config.lisp | ||
README.md |
Nix + Google Cloud Run (i.e. GCR)
I'm documenting how I currently deploy projects that I package with Nix on Google Cloud Run.
I'd like to automate this workflow as much as possible, and I intend to do just that. For now, I'm running things manually until I can design an generalization that appeals to me.
Dependencies
nix-build
docker
gcloud
Step-by-step
- Use
nix-build
to create our Docker image for Cloud Run.
> nix-build ./cloud_run.nix
This outputs a Docker image at ./result
.
- Load the built image (i.e.
./result
) intodocker
so that we can tag it and push it to the Google Container Registry (i.e. GCR).
> sudo docker load <./result
- (Optionally) Run the image locally to verify its integrity.
> sudo docker run -d -p 8080:4242 <name>:<tag>
- Tag and push the image to GCR.
> sudo docker tag <name>:<label> gcr.io/<google-cloud-project-id>/<name>:<latest>
- Visit Google Cloud Run; create a new service with "Create Service"; select the uploaded Docker image from the "Container Image URL" field; click "Create" to deploy.
Notes
You may need to authorize gcloud
by running the following:
> sudo gcloud auth login --no-launch-browser
You must use sudo
here since the docker
invocations are prefixed with sudo
as well.
Todos
- If possible, prefer using a command line tool like
gcloud
to create the Cloud Run service.