apple/container

[Bug]: `--tmpfs` option for `container {create|run}` does not split mount options.

Open

#2,094 opened on Aug 7, 2026

View on GitHubContributor guide
 (2 comments) (0 reactions) (1 assignee)Swift (752 forks)batch import
help wantedstorage

Repository metrics

Stars
 (26,498 stars)
PR merge metrics
 (Avg merge 1d 17h) (60 merged PRs in 30d)

Description

I have done the following

  • I have searched the existing issues
  • If possible, I've reproduced the issue using the 'main' branch of this project

Steps to reproduce

% container run -it --rm --tmpfs /mnt/scratch:rw,exec alpine ls /mnt
scratch:rw,exec

Problem description

The --tmpfs option should split its value into one or two components (destination path and optional mount options) on the first colon.

The destination path must be a non-empty absolute path.

The mount deduplication should key on the lexically normalized destination path only, not the entire option string.

Validating mount options – not done today, we can continue to let invalid mounts fail in the container – is not in scope for the bug fix.

Environment

- OS: 26
- Xcode: 26
- Container: main

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Locate where the ` tmpfs` flag is parsed by searching for `tmpfs` in the codebase. The current code likely passes the whole value as the mount destination. Modify it to split on the first colon into destination and optional options, validate the destination is a non empty absolute path, and update mount deduplication to key on the normalized destination path. Add or update tests covering the split behavior.
Tech stack
swift
Domain
backendcli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitSwift
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75