Daisuke cf76a69948 feat(dev): add Podman-based container workflow

- Add Containerfile for running Astro dev server in a container
- Add compose.yml (slirp4netns) for WSL2/rootless compatibility
- Document Podman compose usage and troubleshooting steps in README
- Ignore optional Podman env file in .gitignore

2026-01-31 19:54:28 +09:00

1.5 KiB

Raw Blame History

Naputo - n-daisuke897's blog

Welcome to my blog repository!

Commands

All commands are run from the root of the project, from a terminal:

Command	Action
`npm install`	Installs dependencies
`npm run dev`	Starts local dev server at `localhost:4321`
`npm run build`	Build your production site to `./dist/`
`npm run preview`	Preview your build locally, before deploying
`npm run astro ...`	Run CLI commands like `astro add`, `astro check`
`npm run astro -- --help`	Get help using the Astro CLI

Podman (container) development

This repo can be developed inside a Podman container to keep your host clean and improve reproducibility.

Using podman compose

podman compose up --build

On WSL2/rootless Podman, if you hit netavark/nftables errors, this repo defaults to slirp4netns via network_mode in compose.yml.

Then open: http://localhost:4321

Run other commands in the running container:

podman compose exec app npm run build
podman compose exec app npm run preview -- --host 0.0.0.0 --port 4321

Troubleshooting (WSL2)

If hot reload is unstable/slow, enable polling:

CHOKIDAR_USEPOLLING=1 podman compose up --build

Tip: placing the repo under the WSL filesystem (e.g. ~/project/...) is often faster than under /mnt/c.