support project directory with remounted path

Metadata

Project: rockcraft
Number: #583
Type: issue
State: open
Author: henrymao-zz
Labels: —
Created: 2024-06-12 02:10 AM UTC
Updated: 2024-06-12 02:11 AM UTC
Closed: —

Current evaluation

Feature request: rockcraft should support bind-mounted (remounted) paths inside the project directory, which are currently invisible during packaging because the project dir is copied into the build environment. No maintainer activity, labels, or comments in ~2.2 years.

Suggested action: needs triage

Reason: The issue has zero maintainer interaction, no labels, and no comments in ~810 days, so it has never been triaged or categorised. It is a legitimate feature request (bind-mounted project subdirs are dropped when the project dir is copied into the build environment), not a support question, so it should be assessed rather than closed. I could not find any commit, PR, or related issue addressing bind-mount support, so I cannot confirm it is fixed or obsolete.

Impact: 40 Quick Win: 14.0 Staleness: 88 Complexity: 65 Confidence: 55 Support Request: 20

Issue body

### What needs to get done Mounted path are not accessible at rockcraft packaging time. In the following example, "debs" in project directory is mounted from another directory. Contents in "debs" are not visible in rockcraft shell, and not accessible during image packing. ``` #sudo mount --bind ../../target/debs/jammy/ debs #rockcraft stage --shell rockcraft-docker-lldp-on-amd64-for-amd64-3099612 ../project# ls debs rockcraft-docker-lldp-on-amd64-for-amd64-3099612 ../project# exit exit #mount | grep debs /dev/xvda1 on /home/ubuntu/sonic-buildimage/dockers/docker-lldp/debs type ext4 (rw,relatime,discard,errors=remount-ro) sudo mount --bind ../../target/debs/jammy/ debs ``` Below is another failure log: ``` Building my-part :: + ls mounted original rockcraft.yaml :: rockcraft.yaml :: :: mounted: :: :: original: :: myfile :: + cp mounted/myfile /root/parts/my-part/install/myfile :: cp: cannot stat 'mounted/myfile': No such file or directory 'override-build' in part 'my-part' failed with code 1. Recommended resolution: Review the scriptlet and make sure it's correct. Failed to execute rockcraft in instance. Full execution log: '/home/cris/.local/state/rockcraft/log/rockcraft-20240606-160506.454710.log' cris@cris-laptop:/tmp/tmp.d7zfXGzS4A $ ls mounted/ myfile ``` ### Why it needs to get done Mounted path are useful to handle large amount of files produced in earlier phases of build.

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 01:43 AM UTC	qwen/qwen3.8-27b	Impact: 40 Quick Win: 14.0 Staleness: 88 Complexity: 65 Confidence: 55 Support Request: 20	needs triage	Feature request: rockcraft should support bind-mounted (remounted) paths inside the project directory, which are currently invisible during packaging because the project dir is copied into the build environment. No maintainer activity, labels, or comments in ~2.2 years.
2026-07-22 12:09 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 92 Complexity: 65 Confidence: 85 Support Request: 20	needs triage	Unresolved request to support bind-mounted paths in the project directory during rockcraft build and shell execution. No maintainer response or labels after 770 days.
2026-07-08 07:22 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 70 Confidence: 85 Support Request: 20	close stale	Unaddressed request to support bind-mounted directories in Rockcraft project paths. Build stages fail to access mounted contents. Issue is 756 days old with zero maintainer interaction.
2026-07-05 10:03 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 70 Confidence: 80 Support Request: 10	needs triage	Unassessed report that bind-mounted directories in project paths are inaccessible during rockcraft build and shell stages. No maintainer response or labels after over two years.
2026-06-16 11:46 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 92 Complexity: 65 Confidence: 70 Support Request: 20	needs triage	Rockcraft cannot access bind-mounted directories in the project path during packaging and stage phases. The request remains open, unassigned, and inactive for over two years with no comments or triage.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.