Gemini CLI image with directories and .env config setup
1.2K
This repository contains Docker files and recommended configurations for a quick and minimal setup of the Google Gemini CLI, installing it in an isolated container to avoid direct installation in a host machine.
This image is only for local development purposes.
GitHub Repository
https://github.com/weaponsforge/gemini-cli
Pull the "latest" development image.
docker pull weaponsforge/gemini-cli
Create a .env file from the .env.example file. Replace the value of the GEMINI_API_KEY with your own Google Gemini API key.
Copy existing projects into sub-directories following the basic projects folder structure. It requires having the sub-project directories inside the /projects directory in the host machine, e.g.,
├─ .env
├─ projects
│ ├─ my-app
│ ├─ cool-website
│ ├─ my-portfolio
│ ├─ ...
WARNING: Avoid including the sub-projects' installation dependencies (e.g., /node_modules) to minimize the number of files/codes reflected in the Docker container (since it uses bind-mount.)
Run the development image.
Navigate to the parent directory that contains the "project" directory and the .env file using a terminal, then run:
# Using PowerShell
docker run -it -v ${pwd}/projects:/opt/app/projects --env-file .env --rm weaponsforge/gemini-cli gemini
TIPS:
Content type
Image
Digest
sha256:3b109c8b3…
Size
118.9 MB
Last updated
about 1 year ago
docker pull weaponsforge/gemini-cli