cannot change profile for the next exec call: No such file or directory

Metadata

Project: snapcraft (launchpad)
Number: #1760514
Type: issue
State: open
Author: ~popey
Labels: —
Created: 2018-04-02 12:02 AM UTC
Updated: 2018-04-24 09:59 AM UTC
Closed: —

Current evaluation

Snapcraft 2.40 container build (SNAPCRAFT_CONTAINER_BUILDS=1) fails on re-run after a failed build with 'cannot change profile for the next exec call: No such file or directory'; a clean fixes it. Unlabeled, no maintainer response, 0 comments, ~8.4 years old.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and zero comments — no sign a maintainer has ever assessed it, so it defaults to needs_triage. It is a genuine bug report (reproducible container-exec failure on re-run, fixed by clean) rather than a support question, but it is ~8.4 years old and targets snapcraft 2.40/snapd 2.32.1 on 16.04, a long-unsupported stack, so it is very stale and likely no longer reproducible on current versions.

Impact: 40 Quick Win: 14.0 Staleness: 95 Complexity: 65 Confidence: 55 Support Request: 25

Issue body

I have hit this a bunch of times recently on my 16.04 KDE Neon machine. It only happens if I set SNAPCRAFT_CONTAINER_BUILDS=1, run a build (which fails) and then re-run the build again. Here you can see the end of a failure, me re-running and it failing, then me doing a clean and re-running and it works. alan@KinkPad-K450:~/src/cointop$ snap version snap 2.32.1 snapd 2.32.1 series 16 neon 16.04 kernel 4.13.0-37-generic alan@KinkPad-K450:~/src/cointop$ snapcraft --version snapcraft, version 2.40+git3.b6ed5ac File "/snap/snapcraft/1337/lib/python3.6/site-packages/snapcraft/internal/pluginhandler/__init__.py", line 363, in build script_runner.run(scriptlet=self._part_properties.get('prepare')) File "/snap/snapcraft/1337/lib/python3.6/site-packages/snapcraft/internal/pluginhandler/_scriptlets.py", line 43, in run run([scriptlet_path], cwd=self._builddir) File "/snap/snapcraft/1337/lib/python3.6/site-packages/snapcraft/internal/common.py", line 64, in run subprocess.check_call(['/bin/sh', f.name] + cmd, **kwargs) File "/snap/snapcraft/1337/usr/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/bin/sh', '/tmp/tmplp53fzcu', '/tmp/tmpm286qh9h']' returned non-zero exit status 128. You can anonymously report this issue to the snapcraft developers. No other data than this traceback and the version of snapcraft in use will be sent. Would you like send this error data? [y/N]: n Stopping local:snapcraft-cointop alan@KinkPad-K450:~/src/cointop$ snapcraft Using default LXD remote because SNAPCRAFT_CONTAINER_BUILDS is set to 1 Device /root/build_cointop removed from snapcraft-cointop Waiting for a network connection... Network connection established Mounting /home/alan/src/cointop into container Device /root/build_cointop added to snapcraft-cointop cannot change profile for the next exec call: No such file or directory Stopping local:snapcraft-cointop alan@KinkPad-K450:~/src/cointop$ snapcraft clean Deleting local:snapcraft-cointop Cleaning up priming area Cleaning up staging area Cleaning up parts directory alan@KinkPad-K450:~/src/cointop$ snapcraft Using default LXD remote because SNAPCRAFT_CONTAINER_BUILDS is set to 1 Creating snapcraft-cointop Device fuse added to snapcraft-cointop Waiting for a network connection... Network connection established Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:3 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7532 kB]

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 08:14 AM UTC	qwen/qwen3.8-27b	Impact: 40 Quick Win: 14.0 Staleness: 95 Complexity: 65 Confidence: 55 Support Request: 25	needs triage	Snapcraft 2.40 container build (SNAPCRAFT_CONTAINER_BUILDS=1) fails on re-run after a failed build with 'cannot change profile for the next exec call: No such file or directory'; a clean fixes it. Unlabeled, no maintainer response, 0 comments, ~8.4 years old.
2026-07-23 11:55 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 100 Complexity: 25 Confidence: 95 Support Request: 85	close stale	Reported snapcraft 2.40 error on Ubuntu 16.04 when re-running container builds. Over 8 years old, no maintainer interaction, and irrelevant to current versions.
2026-07-22 12:20 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 98 Complexity: 20 Confidence: 95 Support Request: 15	close stale	Snapcraft build fails on re-run with LXD container error on Ubuntu 16.04. No maintainer response in over 8 years.
2026-07-09 11:33 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 25 Confidence: 92 Support Request: 15	close stale	Snapcraft container build fails on re-run with 'cannot change profile' error. Issue is over 8 years old, targets EOL Ubuntu 16.04 and Snapcraft 2.40, and has zero maintainer activity.
2026-06-21 01:43 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 30 Confidence: 90 Support Request: 15	close stale	Bug report for snapcraft 2.40 on Ubuntu 16.04 where re-running a failed container build fails with a profile exec error. Requires a clean to resolve. Unlabelled and inactive for over 8 years.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.