Run clasp in a Docker container, for developing Google Apps Script in your local machine.

## Build container (optional)
docker build -t serandel/clasp .

## Execute clasp
docker run --rm -it -v $(pwd):/app -v clasp:/home/node serandel/clasp login --no-localhost
docker run --rm -it -v $(pwd):/app -v clasp:/home/node serandel/clasp push

This way you can login without the need to open any ports and your config file will be created in a Docker volume, to be shared between all the container instances.

For easier usage, add the following to your .bashrc or .zshrc:

alias clasp='docker run --rm -it -v $(pwd):/app -v clasp:/home/node serandel/clasp --no-localhost'

(Beware, if you use double quotes in the alias the pwd command will be resolved during login, not when you run the command...)

And now just:

clasp login --no-localhost

clasp push

Clasp opens a random port when doing a login with Google, and opening wide range of ports in Docker is inefficient and will possibly eat up all of your RAM, as you can see in this 5-year old bug. It's much advised to use the login --no-localhost option, which will simply require you to copy and paste a string from a webpage to the terminal.

The container has the Typescript definitions for Google Apps Script installed globally. It's suitable, thus, for developing in Typescript, using the remote capabilities of Visual Studio Code. Just keep the container open with, for example:

clasp logs --watch

And in a Visual Studio Code instance with the Remote-Containers add-on, choose Attach to running container... from the Command Palette. This will use the Clasp Node.js instance to compile your Typescript code.