alpine and arch sometimes use sha512, main snapd fail to start
Bug #1850914 reported by
Zygmunt Krynicki
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Fix Released
|
High
|
Maciej Borzecki | ||
Bug Description
As seen in this Arch Linux AUR thread: https:/
In some cases, the toolchain uses she-512 based build IDs, making snapd fail to identify snap-seccomp version. It is unclear why this happens. Maciej separately conveyed that a similar issue affected Alpine as well.
Revision history for this message
| Maciej Borzecki (maciek-borzecki) wrote | #1 |
| Changed in snapd: | |
| assignee: | nobody → Maciej Borzecki (maciek-borzecki) |
| status: | Confirmed → In Progress |
Revision history for this message
| Maciej Borzecki (maciek-borzecki) wrote | #2 |
| Changed in snapd: | |
| status: | In Progress → Fix Committed |
| Changed in snapd: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The user reported seeing this problem in the logs:
$ sudo journalctl -u snapd.service
...
cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: invalid format of version-info: "6f33567a6d5533
Similar issue was reported on Alpine in https:/
2019/09/11 21:26:31.393539 daemon.go:346: started snapd/unknown (series 16; classic; devmode) alpine/
cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: invalid format of version-info: “43426b4f715267