containerd / containerd/nerdctl

compose: have an option to resolve `~` into the host home directory of Lima / Rancher Desktop

Open
#996 4 comments 7 reactions 0 assignees View on GitHub
kind/external kind/external/lima kind/external/rancher-desktop kind/feature
Dominant language
Go
Stars
10.4k
Forks
826
Avg merge
1d 23h
Merged PRs (30d)
46

Description

### What is the problem you're trying to solve

`nerdctl compose up` via Lima or Rancher Desktop resolves `~` in the compose YAML into the guest home `(/home/foo.linux` or `/root`), not into the host home (`/Users/foo`).

This is not a bug but confusing.

### Describe the solution you'd like

Support a new property like `home = $LIMA_USERHOME` in `nerdctl.toml`:
https://github.com/containerd/nerdctl/blob/master/docs/config.md

Probably this can be applied to expansion of `~/.docker/config.json` too.

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with docs/config.md and trace how nerdctl compose expands `~` in Compose YAML when running through Lima or Rancher Desktop. Determine where a `home = $LIMA_USERHOME` option would be read and whether the same behavior applies to `~/.docker/config.json`; done means the configured host home is used instead of the guest home.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.