snapcraft container builds with snap try
Metadata
Current evaluation
Abandoned. The container build cp error during snap try remains unfixed due to age and lack of developer activity.
Suggested action: —
No scores available.
Issue body
If you `snap try prime` in the snapcraft directory when container builds are enabled, a cp traceback is raised as the code is expecting a file copy instead of a directory, we should error out correctly (unsupported) and/or support it.
Making snapcraft_x4.snap user-accessible
cp: -r not specified; omitting directory '/var/lib/snapd/snaps/snapcraft_x4.snap'
Stopping local:snapcraft-hooks
Traceback (most recent call last):
File "/snap/snapcraft/x4/bin/snapcraft", line 11, in <module>
load_entry_point('snapcraft==2.34', 'console_scripts', 'snapcraft')()
File "/snap/snapcraft/x4/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 565, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/snap/snapcraft/x4/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2631, in load_entry_point
return ep.load()
File "/snap/snapcraft/x4/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2291, in load
return self.resolve()
File "/snap/snapcraft/x4/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2297, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/cli/__main__.py", line 19, in <module>
run(prog_name='snapcraft')
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 722, in __call__
return self.main(*args, **kwargs)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 1043, in invoke
return Command.invoke(self, ctx)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/cli/__init__.py", line 118, in run
ctx.forward(lifecyclecli.commands['snap'])
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 553, in forward
return self.invoke(cmd, **kwargs)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/cli/lifecycle.py", line 137, in snap
container_config, output, directory)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/internal/lifecycle/_containers.py", line 51, in containerbuild
metadata=config.get_metadata()).execute(step, args)
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/internal/lxd/_containerbuild.py", line 131, in execute
self._inject_snapcraft()
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/internal/lxd/_containerbuild.py", line 203, in _inject_snapcraft
self._inject_snap('snapcraft')
File "/snap/snapcraft/x4/lib/python3.6/site-packages/snapcraft/internal/lxd/_containerbuild.py", line 246, in _inject_snap
subprocess.check_call(['sudo', 'cp', installed, filepath])
File "/snap/snapcraft/x4/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', 'cp', '/var/lib/snapd/snaps/snapcraft_x4.snap', '/home/sergiusens/snap/lxd/common/snapcraftflm_wnwd/snapcraft_x4.snap']' returned non-zero exit status 1.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The container build cp error during snap try remains unfixed due to age and lack of developer activity. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The container build process crashed with a cp traceback when using snap try prime, as it incorrectly attempted to copy a directory instead of a file. Likely abandoned or superseded by newer container architecture. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The reported cp directory error during container builds with snap try prime was not addressed, likely abandoned due to age and lack of activity. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Closed without resolution or comments after over eight years. The container build directory copy error was never addressed. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2014963 Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | snapcraft (launchpad) | open | Snapcraft fails when using snap try due to snapd not allowing file downloads for try-mode snaps. Issue is 1251 days old with no maintainer engagement. | |
| #1805212 snapcraft try (integrated with build environments) | snapcraft (launchpad) | closed | Closed with no comments or resolution details. The feature to integrate snapcraft try with build environments was likely abandoned or superseded by later releases. | |
| #1746381 snapcraft cleanbuild shouldn't always delete container at end | snapcraft (launchpad) | closed | Closed without implementation. The request to preserve the container after a successful build for debugging was not addressed, likely abandoned or superseded by newer workflows. | |
| #1788654 snapcraft cleanbuild doesn't work with cross-compile stage-packages | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft cleanbuild fails during cross-compilation because it does not automatically configure multi-arch package support inside the container. No fix was implemented, and the report appears abandoned. | |
| #1956216 Snapcraft is no longer working within a Docker container | snapcraft (launchpad) | closed | Closed without resolution. The report detailed a snapcraft ModuleNotFoundError in Docker containers, but received no comments or fixes. The issue remains abandoned. | |
| #1670100 Snapcraft includes files from installed snaps in new snap | snapcraft (launchpad) | closed | Abandoned due to inactivity. Snapcraft incorrectly bundled files from previously installed snaps into new builds, but no fix or follow-up was provided. | |
| #1816042 snapcraft cleanbuild fails if container isn't fully ready | snapcraft (launchpad) | closed | The issue describing snapcraft cleanbuild failures when the container is not fully ready was closed. | |
| #1978844 snapcraft try not available for core22-based snap | snapcraft (launchpad) | closed | Closed without resolution or comments. The snapcraft try command remains unavailable for core22-based snaps, with attempts failing or falling back to legacy implementations. | |
| #1570706 Snapcraft cleanbuild command doesn't work | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned or superseded. The cleanbuild command failed due to LXC hash format incompatibility and container stop errors. | |
| #1892551 snapcraft fails to run if it is installed as a try snap | snapcraft (launchpad) | open | Snapcraft 4.x fails when installed via 'snap try': the LXD build provider tries to download the host snapcraft snap file from snapd, which returns 400 for try snaps. Unlabelled, 0 comments, ~6 years old, never triaged. |