alfresco-ng2-components/docs/dev-containers.md

Dev Containers

This repository includes a Dev Container configuration to provide a consistent local development environment in VS Code.

What It Provides

• Node-based development image defined in .devcontainer/Dockerfile
• Workspace configuration in .devcontainer/devcontainer.json
• pnpm provisioned by Corepack from package.json#packageManager (single source of truth)
• Non-root development user configuration (node)
• Persistent pnpm store volume for faster reinstall times

Daily Workflow

1. Open the repository in VS Code.
2. Run Dev Containers: Rebuild and Reopen in Container when prompted (or from Command Palette).
3. Wait for the post-create step to finish package installation.
4. Work as usual: run tests, lint, and Nx targets from the integrated terminal.

Typical day-to-day actions:

• Rebuild after changing .devcontainer/Dockerfile or .devcontainer/devcontainer.json
• Reopen in container after dependency or toolchain updates
• Keep local Docker Desktop running before opening the container

Running Nx Targets From the Workspace

From the repository root (inside the container terminal), run Nx targets with the package manager wrapper.

Common examples:

• pn nx test <project>
• pn nx build <project>

You can replace <project> with any workspace project name, for example core, content-services, or process-services-cloud.

Tip: to discover available projects and targets, run pn nx show projects and inspect each project's project.json (or workspace configuration).

Nx Daemon and Graph Ports in Dev Containers

For this repository's VS Code Dev Container, Nx daemon is enabled (NX_DAEMON=true) to speed up repeated local Nx commands by keeping project graph state warm between runs.

Notes:

• Avoid forcing CI=true in day-to-day dev containers if you want daemon benefits.
• Keep CI=true for real CI pipelines and short-lived/ephemeral containers.
• If needed, disable daemon for a single command with NX_DAEMON=false pn nx <target>.

When running Nx commands, VS Code may show a notification about a port being opened by Nx Graph. This is expected when Nx serves the graph UI locally; it is typically a localhost-only temporary port used for visualization.

Git Operations and Signing

The container is set up so you can do all Git work — including signed commits and pushes — inside it, using your host credentials and settings. Your private keys never enter the container: only the agent socket is forwarded.

Option A: Commit and Sign in Container (Recommended)

The VS Code Dev Containers extension wires this up automatically:

• Your host .gitconfig (including user.signingkey and commit.gpgsign) is copied into the container.
• Your host gpg-agent is forwarded (this is why gnupg2 is installed in the image), and your GPG public keys are imported into the container.
• Your host SSH agent is forwarded, so git push over SSH uses your host keys.

One-time host setup (this is what gets copied in):

git config --global user.signingkey <YOUR_KEY_ID>
git config --global commit.gpgsign true

Then work entirely inside the container:

gpg --list-secret-keys            # verify the forwarded key is visible
git commit -S -m "your message"   # -S optional when commit.gpgsign is true
git push

If signing fails with gpg failed to sign the data / no secret key, the agent forwarding did not attach — rebuild the container or reload the VS Code window.

Note: the automatic gitconfig / GPG / SSH forwarding is a feature of the VS Code Dev Containers extension. If you run this configuration via the plain @devcontainers/cli, mount ~/.gnupg, ~/.gitconfig, and the agent sockets yourself, or fall back to Option B.

Option B: Sign Commits on Host

For the strongest key isolation, keep signing on the host:

• Keep private signing keys only on the host.
• Do normal development in the container.
• Stage and commit from a host terminal in the same repository checkout (for example, git commit -S ...).

Good fit when your policy forbids forwarding signing agents into containers.

Option C: Unsigned Commits in Container, Signed Merge in CI/Host

• Commit in container without local signing.
• Enforce signing at merge/release time using host or CI controls.

This can simplify local setup for contributors while preserving integrity checks in protected branches.

Practical Daily Pattern

1. Code, lint, and test in the container.
2. Commit and sign in the container using the forwarded host keys.
3. Push from the container (SSH agent or gh credentials are forwarded).
4. Keep branch protection checks active (status checks, review, signature policy if used).

Updating Base Image Safely

When updating the base image digest in .devcontainer/Dockerfile:

• Keep the FROM line digest-pinned for reproducibility
• Do not add an inline trailing comment on the same FROM line
• Put comments on separate lines above the FROM line

Why: some Docker/Buildx parser combinations can fail with:

FROM requires either one or three arguments

even when the digest itself is valid.

Quick Troubleshooting

If container startup fails:

1. Verify Docker Desktop is running.
2. Build the Dockerfile directly to isolate parser/build issues.
3. Rebuild and Reopen in Container after fixes.

Useful files to inspect:

• .devcontainer/devcontainer.json
• .devcontainer/Dockerfile
• VS Code Dev Containers logs under your local VS Code logs directory

Nx Daemon Not Starting in Container

If NX_DAEMON=true is set but pn nx daemon still reports that the daemon is not running, Nx may have persisted a stale disable marker from a previous startup failure.

Recovery steps:

1. Reset Nx local state:

   pnpm nx reset
   

2. Run any Nx command to trigger daemon startup:

   pnpm nx show projects
   

3. Verify daemon status:

   pnpm nx daemon
   

4. If still not running, inspect logs:

   cat .nx/workspace-data/d/daemon.log
   

Notes:

• In Docker/dev containers, Nx disables daemon by default unless explicitly enabled.
• This repository enables it via NX_DAEMON=true in .devcontainer/devcontainer.json.