← Back to issue list

The base field created by snapcraft init should match the docker equivalent image or raise an error

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1830388
Type
issue
State
closed
Author
~ev
Labels
Created
Updated
Closed

Current evaluation

Closed as stale. Superseded by infrastructure changes; Snapcraft's Dockerfiles were updated and migrated to rocks, resolving the base mismatch without code changes.

Suggested action:

No scores available.

Issue body

(See also https://bugs.launchpad.net/snapcraft/+bug/1830389) Running snapcraft init inside the 16.04 snapcore/snapcraft docker produces a snapcraft.yaml with base: core18. You'll likely add some *-packages and this will break. Snapcraft init should select base: core if inside a 16.04 Docker, base: core18 if in 18.04 Docker, or error otherwise. It may be worth moving the snapcore/snapcraft:latest, :beta, and :candidate images to 18.04 (but worth weighing the impact to existing users). ~/example❯ docker run -v $(pwd):$(pwd) -w $(pwd) snapcore/snapcraft:beta snapcraft init Locale not set! Snapcraft will temporarily use C.UTF-8 Created snap/snapcraft.yaml. Go to https://docs.snapcraft.io/the-snapcraft-format/8337 for more information about the snapcraft.yaml format. ~/example❯ cat snap/snapcraft.yaml name: my-snap-name # you probably want to 'snapcraft register <name>' base: core18 # the base snap is the execution environment for this snap version: '0.1' # just for humans, typically '1.2+git' or '1.3.2' summary: Single-line elevator pitch for your amazing snap # 79 char long summary description: |   This is my-snap's description. You have a paragraph or two to tell the   most important story about your snap. Keep it under 100 words though,   we live in tweetspace and your description wants to look good in the snap   store. grade: devel # must be 'stable' to release into candidate/stable channels confinement: devmode # use 'strict' once you have the right plugs and slots parts:   my-part:     # See 'snapcraft plugins'     plugin: nil

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed as stale. Superseded by infrastructure changes; Snapcraft's Dockerfiles were updated and migrated to rocks, resolving the base mismatch without code changes.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 15
close stale snapcraft init generates a base field mismatched with the Docker environment instead of matching it or raising an error. Unaddressed for 7 years with no maintainer interaction.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 60
Confidence: 90
Support Request: 20
close stale snapcraft init generates an incorrect base field when run inside outdated Docker images. The issue is 7 years old, lacks maintainer engagement, and references deprecated bases no longer supported in modern snapcraft.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 45
Confidence: 85
Support Request: 15
close stale snapcraft init generates an incorrect base field in older Docker containers, causing build failures. The issue is 7 years old, has no maintainer engagement, and references deprecated Ubuntu 16.04 and core18 bases.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 15
close stale snapcraft init generates an incorrect base field when run inside older Docker containers. The report is 7 years old, unlabelled, and references deprecated core18 base.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1826611 Running snapcraft 3 w/ core18 base in docker incorrectly reports missing lib deps snapcraft (launchpad) closed 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.
71%
#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.
70%