Running snapcraft 3 w/ core18 base in docker incorrectly reports missing lib deps
Metadata
Current evaluation
Closed as stale. Snapcraft resolved the issue by updating its Dockerfiles and migrating to OCI rocks for builds, eliminating the incorrect core18 dependency warnings in Docker.
Suggested action: —
No scores available.
Issue body
When building a snap using snapcraft 3.X in a docker container and specifying `base: core18`, snapcraft doesn't attempt to install the core18 snap which is fine since we build inside a ubuntu:18.04 container and have all the needed dependencies, however it then proceeds to claim that executables in the snap need dependencies that are not present in the snap or the base snap. However this is incorrect as all the required libraries are actually in the base snap. For example, when building curl:
```
Priming curl
The 'curl' part needs the following libraries that are not included in the snap or base:
lib/x86_64-linux-gnu/libc.so.6
lib/x86_64-linux-gnu/libcrypt.so.1
lib/x86_64-linux-gnu/libdl.so.2
lib/x86_64-linux-gnu/libm.so.6
lib/x86_64-linux-gnu/libpthread.so.0
lib/x86_64-linux-gnu/libresolv.so.2
lib/x86_64-linux-gnu/libz.so.1
```
All of which are in the core18 snap.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed as stale. Snapcraft resolved the issue by updating its Dockerfiles and migrating to OCI rocks for builds, eliminating the incorrect core18 dependency warnings in Docker. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Snapcraft 3.x with core18 base in Docker incorrectly flags core18-provided libraries as missing during priming. Untriaged, inactive for over 7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Reports snapcraft 3.x incorrectly flagging core18 base libraries as missing during Docker builds. Unanswered for over 7 years; core18 and snapcraft 3.x are long deprecated. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | snapcraft 3 incorrectly flags core18 base libraries as missing during Docker builds. The issue has been inactive for over 7 years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
50
Confidence:
90
Support Request:
10
|
close stale | Snapcraft 3.x with core18 base in Docker incorrectly flags standard system libraries as missing, despite them being provided by the base snap. Untriaged and inactive for ~7 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1830389 misleading warning when building base: core18 snap with 16.04 snapcore/snapcraft docker | snapcraft (launchpad) | closed | Closed as stale. Snapcraft Dockerfiles have changed and migrated to rocks, rendering the original warning context obsolete. No code changes were made. | |
| #2883 docker: add core18 snap that snapcraft now uses as a base | snapcraft | merged | Merged the addition of the core18 snap as snapcraft's Docker base, updating related comments for accuracy. Approved by one reviewer, the change was integrated after a minor authorship clarification. | |
| #4290 docker: add core22 base | snapcraft | closed | Rejected and closed. Maintainers declined the core22 Docker base update due to legacy constraints, directing users to the new snapcraft-rocks initiative. The PR was superseded by canonical/snapcraft-rocks. | |
| #1939713 snapcraft init create base: core18 snap | snapcraft (launchpad) | closed | Closed without direct resolution, likely abandoned due to inactivity. Subsequent Snapcraft releases updated the init default to core20 and core22, effectively resolving the reported behavior. | |
| #1846195 provide snapcraft docker image for core18 | snapcraft (launchpad) | open | Request for canonical-provided core18-based snapcraft docker images (official ones were xenial-based). 7 years old, no comments or labels; core18 is EOL and the project has moved to core20+, so the request is no longer applicable. | |
| #1830388 The base field created by snapcraft init should match the docker equivalent image or raise an error | snapcraft (launchpad) | closed | Closed as stale. Superseded by infrastructure changes; Snapcraft's Dockerfiles were updated and migrated to rocks, resolving the base mismatch without code changes. | |
| #1862256 snapcraft should complain loudly when building base: core20 snap on i386 | snapcraft (launchpad) | closed | Closed as superseded. Improved architecture parsing in snapcraft now correctly rejects unsupported base-architecture combinations, addressing the original request without requiring explicit i386 core20 checks. | |
| #1814024 snapcore/snapcraft stable docker images are out of date | snapcraft (launchpad) | closed | Outdated snapcraft Docker images were reported but the ticket was closed as stale due to inactivity. No fix was implemented. | |
| #5079 Cannot run snapcraft in docker anymore | snapcraft | open | Snapcraft crashes with SnapCtlError when run in Docker without snapd; reporter found a working Dockerfile workaround, maintainer kept it open to improve error handling. Triaged as enhancement, last activity 493 days ago. | |
| #4246 Reported error message building base: core18 with newer snapcrafts is wrong | snapcraft | closed | Closed without resolution. A maintainer noted the error applies to any unsupported base like core17 and suggested improving the message to clarify base incompatibility instead of blaming the plugin. |