Failing to install snapd on pi zero w

snapd
1

Hello, absolute certified novice here - trying and failing to install snapd on pi zero w board, during install I get:

“Job for snapd.service failed because the control process exited with error code. See “systemctl status snapd.service” and “journalctl -xe” for details.”

When I ran systemctl status snapd.service I got the return as copied in below - sorry hope this isn’t too long - I’m very grateful for any help thank you.

pi@testpop1:~ $ sudo systemctl status snapd.service

● snapd.service - Snap Daemon

Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset:>

Active: failed (Result: exit-code) since Mon 2023-05-08 20:41:20 BST; 3min>

TriggeredBy: ● snapd.socket

Process: 1041 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)

Main PID: 1041 (code=exited, status=1/FAILURE)

CPU: 514ms

May 08 20:41:19 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 20:41:19 testpop1 systemd[1]: snapd.service: Scheduled restart job, rest>

May 08 20:41:20 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Start request repeated too >

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Failed with result 'exit-co>

May 08 20:41:20 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Triggering OnFailure= depen>

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Failed to enqueue OnFailure>

lines 1-16/16 (END)…skipping…

● snapd.service - Snap Daemon

Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset:>

Active: failed (Result: exit-code) since Mon 2023-05-08 20:41:20 BST; 3min>

TriggeredBy: ● snapd.socket

Process: 1041 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)

Main PID: 1041 (code=exited, status=1/FAILURE)

CPU: 514ms

May 08 20:41:19 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 20:41:19 testpop1 systemd[1]: snapd.service: Scheduled restart job, rest>

May 08 20:41:20 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Start request repeated too >

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Failed with result 'exit-co>

May 08 20:41:20 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Triggering OnFailure= depen>

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Failed to enqueue OnFailure>

~

lines 1-16/16 (END)…skipping…

● snapd.service - Snap Daemon

Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Mon 2023-05-08 20:41:20 BST; 3min 24s ago

TriggeredBy: ● snapd.socket

Process: 1041 ExecStart=/usr/lib/snapd/snapd (code=exited, status=1/FAILURE)

Main PID: 1041 (code=exited, status=1/FAILURE)

CPU: 514ms

May 08 20:41:19 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 20:41:19 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 17.

May 08 20:41:20 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Start request repeated too quickly.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 20:41:20 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Triggering OnFailure= dependencies.

May 08 20:41:20 testpop1 systemd[1]: snapd.service: Failed to enqueue OnFailure= job, ignoring: Unit snapd.failure.service not found.

2

When I ran “journalctl -xe” I got the below text returned in case this is useful.

pi@testpop1:~ $ sudo journalctl -xe

░░

░░ A session with the ID 4 has been terminated.

May 08 21:40:37 testpop1 sshd[1419]: Accepted password for pi from fe80::1c5d:b>

May 08 21:40:37 testpop1 sshd[1419]: pam_unix(sshd:session): session opened for>

May 08 21:40:37 testpop1 systemd-logind[315]: New session 6 of user pi.

░░ Subject: A new session 6 has been created for user pi

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ Documentation: sd-login(3)

░░

░░ A new session with the ID 6 has been created for the user pi.

░░

░░ The leading process of the session is 1419.

May 08 21:40:37 testpop1 systemd[1]: Started Session 6 of user pi.

░░ Subject: A start job for unit session-6.scope has finished successfully

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A start job for unit session-6.scope has finished successfully.

░░

░░ The job identifier is 2320.

May 08 21:41:08 testpop1 sudo[1437]: pi : TTY=pts/0 ; PWD=/home/pi ; USER>

May 08 21:41:08 testpop1 sudo[1437]: pam_unix(sudo:session): session opened for>

lines 3268-3290/3290 (END)

░░

░░ A session with the ID 4 has been terminated.

May 08 21:40:37 testpop1 sshd[1419]: Accepted password for pi from fe80::1c5d:b20:7c2a:97d9%wlan0 port 51051 ssh2

May 08 21:40:37 testpop1 sshd[1419]: pam_unix(sshd:session): session opened for user pi(uid=1000) by (uid=0)

May 08 21:40:37 testpop1 systemd-logind[315]: New session 6 of user pi.

░░ Subject: A new session 6 has been created for user pi

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░ Documentation: sd-login(3)

░░

░░ A new session with the ID 6 has been created for the user pi.

░░

░░ The leading process of the session is 1419.

May 08 21:40:37 testpop1 systemd[1]: Started Session 6 of user pi.

░░ Subject: A start job for unit session-6.scope has finished successfully

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A start job for unit session-6.scope has finished successfully.

░░

░░ The job identifier is 2320.

May 08 21:41:08 testpop1 sudo[1437]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/journalctl -xe

May 08 21:41:08 testpop1 sudo[1437]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)

~

ESCOC

~

lines 3268-3290/3290 (END)

3

This command didn’t have any relevant information

try sudo journalctl -u snapd.service to get more information about snapd.

4

Thank you for the feedback, below is the output for sudo journalctl -u snapd.service

pi@testpop1:~ $ sudo journalctl -u snapd.service

– Journal begins at Wed 2023-05-03 01:36:12 BST, ends at Tue 2023-05-09 08:40:>

May 08 16:52:53 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:53 testpop1 snapd[1518]: AppArmor status: apparmor not enabled

May 08 16:52:53 testpop1 snapd[1518]: daemon.go:347: started snapd/2.49-1+rpi1+>

May 08 16:52:54 testpop1 snapd[1518]: daemon.go:440: adjusting startup timeout >

May 08 16:52:54 testpop1 snapd[1518]: cannot run daemon: state startup errors: >

May 08 16:52:54 testpop1 snapd[1518]: -----

May 08 16:52:54 testpop1 snapd[1518]: 2023/05/08 16:52:54 unknown kernel arch ">

May 08 16:52:54 testpop1 snapd[1518]: panic: unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: goroutine 1 [running]:

May 08 16:52:54 testpop1 snapd[1518]: log.Panicf(0x630e6d, 0x16, 0x1895f48, 0x1>

May 08 16:52:54 testpop1 snapd[1518]: log/log.go:358 +0x9c

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.dpkgArchFr>

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/ar>

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.DpkgKernel>

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/ar>

May 08 16:52:54 testpop1 snapd[1518]: main.init()

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/cmd/sna>

May 08 16:52:54 testpop1 snapd[1518]: -----]

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Main process exited, code=e>

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Failed with result 'exit-co>

May 08 16:52:54 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: snapd.service: Scheduled restart job, rest>

lines 1-23…skipping…

– Journal begins at Wed 2023-05-03 01:36:12 BST, ends at Tue 2023-05-09 08:40:21 BST. –

May 08 16:52:53 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:53 testpop1 snapd[1518]: AppArmor status: apparmor not enabled

May 08 16:52:53 testpop1 snapd[1518]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:54 testpop1 snapd[1518]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:54 testpop1 snapd[1518]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:54 testpop1 snapd[1518]: -----

May 08 16:52:54 testpop1 snapd[1518]: 2023/05/08 16:52:54 unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: panic: unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: goroutine 1 [running]:

May 08 16:52:54 testpop1 snapd[1518]: log.Panicf(0x630e6d, 0x16, 0x1895f48, 0x1, 0x1)

May 08 16:52:54 testpop1 snapd[1518]: log/log.go:358 +0x9c

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x1814936, 0x6, 0x0, 0x189c51c)

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x62b00c, 0x5)

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:54 testpop1 snapd[1518]: main.init()

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:54 testpop1 snapd[1518]: -----]

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:54 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.

May 08 16:52:55 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:55 testpop1 snapd[1541]: AppArmor status: apparmor not enabled

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 1…

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 2…

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 3…

May 08 16:52:55 testpop1 snapd[1541]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:56 testpop1 snapd[1541]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:56 testpop1 snapd[1541]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:56 testpop1 snapd[1541]: -----

May 08 16:52:56 testpop1 snapd[1541]: 2023/05/08 16:52:56 unknown kernel arch “armv6l”

May 08 16:52:56 testpop1 snapd[1541]: panic: unknown kernel arch “armv6l”

May 08 16:52:56 testpop1 snapd[1541]: goroutine 1 [running]:

May 08 16:52:56 testpop1 snapd[1541]: log.Panicf(0x5c0e6d, 0x16, 0x895f48, 0x1, 0x1)

May 08 16:52:56 testpop1 snapd[1541]: log/log.go:358 +0x9c

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x814936, 0x6, 0x0, 0x89c51c)

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x5bb00c, 0x5)

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:56 testpop1 snapd[1541]: main.init()

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:56 testpop1 snapd[1541]: -----]

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:56 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.

May 08 16:52:56 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:56 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:56 testpop1 snapd[1556]: AppArmor status: apparmor not enabled

May 08 16:52:57 testpop1 snapd[1556]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:57 testpop1 snapd[1556]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:57 testpop1 snapd[1556]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:57 testpop1 snapd[1556]: -----

May 08 16:52:57 testpop1 snapd[1556]: 2023/05/08 16:52:57 unknown kernel arch “armv6l”

May 08 16:52:57 testpop1 snapd[1556]: panic: unknown kernel arch “armv6l”

May 08 16:52:57 testpop1 snapd[1556]: goroutine 1 [running]:

May 08 16:52:57 testpop1 snapd[1556]: log.Panicf(0x570e6d, 0x16, 0x2895f48, 0x1, 0x1)

May 08 16:52:57 testpop1 snapd[1556]: log/log.go:358 +0x9c

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x2814936, 0x6, 0x0, 0x289c51c)

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x56b00c, 0x5)

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:57 testpop1 snapd[1556]: main.init()

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:57 testpop1 snapd[1556]: -----]

May 08 16:52:57 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:57 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:57 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:58 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.

May 08 16:52:58 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:58 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:58 testpop1 snapd[1571]: AppArmor status: apparmor not enabled

May 08 16:52:58 testpop1 snapd[1571]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:58 testpop1 snapd[1571]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:59 testpop1 snapd[1571]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:59 testpop1 snapd[1571]: -----

May 08 16:52:59 testpop1 snapd[1571]: 2023/05/08 16:52:58 unknown kernel arch “armv6l”

lines 1-80

– Journal begins at Wed 2023-05-03 01:36:12 BST, ends at Tue 2023-05-09 08:40:21 BST. –

May 08 16:52:53 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:53 testpop1 snapd[1518]: AppArmor status: apparmor not enabled

May 08 16:52:53 testpop1 snapd[1518]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:54 testpop1 snapd[1518]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:54 testpop1 snapd[1518]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:54 testpop1 snapd[1518]: -----

May 08 16:52:54 testpop1 snapd[1518]: 2023/05/08 16:52:54 unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: panic: unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: goroutine 1 [running]:

May 08 16:52:54 testpop1 snapd[1518]: log.Panicf(0x630e6d, 0x16, 0x1895f48, 0x1, 0x1)

May 08 16:52:54 testpop1 snapd[1518]: log/log.go:358 +0x9c

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x1814936, 0x6, 0x0, 0x189c51c)

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x62b00c, 0x5)

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:54 testpop1 snapd[1518]: main.init()

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:54 testpop1 snapd[1518]: -----]

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:54 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.

May 08 16:52:55 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:55 testpop1 snapd[1541]: AppArmor status: apparmor not enabled

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 1…

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 2…

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 3…

May 08 16:52:55 testpop1 snapd[1541]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:56 testpop1 snapd[1541]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:56 testpop1 snapd[1541]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:56 testpop1 snapd[1541]: -----

May 08 16:52:56 testpop1 snapd[1541]: 2023/05/08 16:52:56 unknown kernel arch “armv6l”

May 08 16:52:56 testpop1 snapd[1541]: panic: unknown kernel arch “armv6l”

May 08 16:52:56 testpop1 snapd[1541]: goroutine 1 [running]:

May 08 16:52:56 testpop1 snapd[1541]: log.Panicf(0x5c0e6d, 0x16, 0x895f48, 0x1, 0x1)

May 08 16:52:56 testpop1 snapd[1541]: log/log.go:358 +0x9c

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x814936, 0x6, 0x0, 0x89c51c)

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x5bb00c, 0x5)

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:56 testpop1 snapd[1541]: main.init()

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:56 testpop1 snapd[1541]: -----]

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:56 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.

May 08 16:52:56 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:56 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:56 testpop1 snapd[1556]: AppArmor status: apparmor not enabled

May 08 16:52:57 testpop1 snapd[1556]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:57 testpop1 snapd[1556]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:57 testpop1 snapd[1556]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:57 testpop1 snapd[1556]: -----

May 08 16:52:57 testpop1 snapd[1556]: 2023/05/08 16:52:57 unknown kernel arch “armv6l”

May 08 16:52:57 testpop1 snapd[1556]: panic: unknown kernel arch “armv6l”

May 08 16:52:57 testpop1 snapd[1556]: goroutine 1 [running]:

May 08 16:52:57 testpop1 snapd[1556]: log.Panicf(0x570e6d, 0x16, 0x2895f48, 0x1, 0x1)

May 08 16:52:57 testpop1 snapd[1556]: log/log.go:358 +0x9c

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x2814936, 0x6, 0x0, 0x289c51c)

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x56b00c, 0x5)

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:57 testpop1 snapd[1556]: main.init()

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:57 testpop1 snapd[1556]: -----]

May 08 16:52:57 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:57 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:57 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:58 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.

May 08 16:52:58 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:58 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:58 testpop1 snapd[1571]: AppArmor status: apparmor not enabled

May 08 16:52:58 testpop1 snapd[1571]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:58 testpop1 snapd[1571]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

lines 1-77

– Journal begins at Wed 2023-05-03 01:36:12 BST, ends at Tue 2023-05-09 08:40:>

May 08 16:52:53 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:53 testpop1 snapd[1518]: AppArmor status: apparmor not enabled

May 08 16:52:53 testpop1 snapd[1518]: daemon.go:347: started snapd/2.49-1+rpi1+>

May 08 16:52:54 testpop1 snapd[1518]: daemon.go:440: adjusting startup timeout >

May 08 16:52:54 testpop1 snapd[1518]: cannot run daemon: state startup errors: >

May 08 16:52:54 testpop1 snapd[1518]: -----

May 08 16:52:54 testpop1 snapd[1518]: 2023/05/08 16:52:54 unknown kernel arch ">

May 08 16:52:54 testpop1 snapd[1518]: panic: unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: goroutine 1 [running]:

May 08 16:52:54 testpop1 snapd[1518]: log.Panicf(0x630e6d, 0x16, 0x1895f48, 0x1>

May 08 16:52:54 testpop1 snapd[1518]: log/log.go:358 +0x9c

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.dpkgArchFr>

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/ar>

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.DpkgKernel>

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/ar>

May 08 16:52:54 testpop1 snapd[1518]: main.init()

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/cmd/sna>

May 08 16:52:54 testpop1 snapd[1518]: -----]

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Main process exited, code=e>

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Failed with result 'exit-co>

May 08 16:52:54 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: snapd.service: Scheduled restart job, rest>

lines 1-23

– Journal begins at Wed 2023-05-03 01:36:12 BST, ends at Tue 2023-05-09 08:40:21 BST. –

May 08 16:52:53 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:53 testpop1 snapd[1518]: AppArmor status: apparmor not enabled

May 08 16:52:53 testpop1 snapd[1518]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:54 testpop1 snapd[1518]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:54 testpop1 snapd[1518]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:54 testpop1 snapd[1518]: -----

May 08 16:52:54 testpop1 snapd[1518]: 2023/05/08 16:52:54 unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: panic: unknown kernel arch “armv6l”

May 08 16:52:54 testpop1 snapd[1518]: goroutine 1 [running]:

May 08 16:52:54 testpop1 snapd[1518]: log.Panicf(0x630e6d, 0x16, 0x1895f48, 0x1, 0x1)

May 08 16:52:54 testpop1 snapd[1518]: log/log.go:358 +0x9c

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x1814936, 0x6, 0x0, 0x189c51c)

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x62b00c, 0x5)

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:54 testpop1 snapd[1518]: main.init()

May 08 16:52:54 testpop1 snapd[1518]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:54 testpop1 snapd[1518]: -----]

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:54 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:54 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.

May 08 16:52:55 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:55 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:55 testpop1 snapd[1541]: AppArmor status: apparmor not enabled

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 1…

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 2…

May 08 16:52:55 testpop1 snapd[1541]: patch.go:64: Patching system state level 6 to sublevel 3…

May 08 16:52:55 testpop1 snapd[1541]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:56 testpop1 snapd[1541]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:56 testpop1 snapd[1541]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:56 testpop1 snapd[1541]: -----

May 08 16:52:56 testpop1 snapd[1541]: 2023/05/08 16:52:56 unknown kernel arch “armv6l”

May 08 16:52:56 testpop1 snapd[1541]: panic: unknown kernel arch “armv6l”

May 08 16:52:56 testpop1 snapd[1541]: goroutine 1 [running]:

May 08 16:52:56 testpop1 snapd[1541]: log.Panicf(0x5c0e6d, 0x16, 0x895f48, 0x1, 0x1)

May 08 16:52:56 testpop1 snapd[1541]: log/log.go:358 +0x9c

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x814936, 0x6, 0x0, 0x89c51c)

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x5bb00c, 0x5)

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:56 testpop1 snapd[1541]: main.init()

May 08 16:52:56 testpop1 snapd[1541]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:56 testpop1 snapd[1541]: -----]

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:56 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:56 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.

May 08 16:52:56 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:56 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:56 testpop1 snapd[1556]: AppArmor status: apparmor not enabled

May 08 16:52:57 testpop1 snapd[1556]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:57 testpop1 snapd[1556]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:57 testpop1 snapd[1556]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:57 testpop1 snapd[1556]: -----

May 08 16:52:57 testpop1 snapd[1556]: 2023/05/08 16:52:57 unknown kernel arch “armv6l”

May 08 16:52:57 testpop1 snapd[1556]: panic: unknown kernel arch “armv6l”

May 08 16:52:57 testpop1 snapd[1556]: goroutine 1 [running]:

May 08 16:52:57 testpop1 snapd[1556]: log.Panicf(0x570e6d, 0x16, 0x2895f48, 0x1, 0x1)

May 08 16:52:57 testpop1 snapd[1556]: log/log.go:358 +0x9c

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch.dpkgArchFromKernelArch(0x2814936, 0x6, 0x0, 0x289c51c)

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch/arch.go:117 +0x460

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch.DpkgKernelArchitecture(0x56b00c, 0x5)

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/arch/arch.go:95 +0x18

May 08 16:52:57 testpop1 snapd[1556]: main.init()

May 08 16:52:57 testpop1 snapd[1556]: github.com/snapcore/snapd/cmd/snap-seccomp/main.go:637 +0x5f0

May 08 16:52:57 testpop1 snapd[1556]: -----]

May 08 16:52:57 testpop1 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE

May 08 16:52:57 testpop1 systemd[1]: snapd.service: Failed with result ‘exit-code’.

May 08 16:52:57 testpop1 systemd[1]: Failed to start Snap Daemon.

May 08 16:52:58 testpop1 systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.

May 08 16:52:58 testpop1 systemd[1]: Stopped Snap Daemon.

May 08 16:52:58 testpop1 systemd[1]: Starting Snap Daemon…

May 08 16:52:58 testpop1 snapd[1571]: AppArmor status: apparmor not enabled

May 08 16:52:58 testpop1 snapd[1571]: daemon.go:347: started snapd/2.49-1+rpi1+deb11u2 (series 16; classic; devmode) raspbian/11 (armel) linux/6.1.21.

May 08 16:52:58 testpop1 snapd[1571]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

May 08 16:52:59 testpop1 snapd[1571]: cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information:

May 08 16:52:59 testpop1 snapd[1571]: -----

May 08 16:52:59 testpop1 snapd[1571]: 2023/05/08 16:52:58 unknown kernel arch “armv6l”

5

There is no support for the armel architecture… only armhf and arm64 are supported by snapd (it is curious how you were even able to install the snapd binary)

6

Ok thank you, I’m guessing the pi zero w is too old to run snapd and only just found a seemingly related previous post here Installing snap on Raspberry Pi fails

Presumably I should be ok with the latest Pi 4 or Pi 400 models? - my goal is to install the gutenprint-printer-app https://snapcraft.io/install/gutenprint-printer-app/raspbian#: and to use the pi as a wireless print server.

7

Well, kind of … ubuntu has never supported the ARMv5 and ARMv6 architectures (which debian calls “armel”) …

Even a Pi2 will work, just not the chipsets of the very first Pi generation (Pi1 and the original PiZero) since that was not ARMv7 compatible… the newer Zero W2 does also work well …

I’d also simply go with ubuntu instead of raspbian on supported hardware, since these devices are actually tested to work well with anything snap related before a release…

1 Like
8

Thank you for the additional information, good to know :+1:

9

I just want to quickly mention that the raspberry pi models with the BCM2835 do have an FPU and thus are “hardfloat” (hf). They don’t have the armv7 extras like thumb2, neon, and vfpv3 so developers will need to disable some features to prevent illegal instructions from being introduced into the resulting binaries since many of these armv7 features are defaults now (looking at you golang)

Here’s a few tidbits from a recently re-imaged pi 1 I have laying around:

pi@raspberrypi1:~ $ cat /proc/cpuinfo 
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2835
Revision	: 000e
Serial		: 00000000fc448a2d
Model		: Raspberry Pi Model B Rev 2

pi@raspberrypi1:~ $ uname -a
Linux raspberrypi1 6.1.21+ #1642 Mon Apr  3 17:19:14 BST 2023 armv6l GNU/Linux

pi@raspberrypi1:~ $ dpkg-architecture --list
DEB_BUILD_ARCH=armhf
DEB_BUILD_ARCH_ABI=eabihf
DEB_BUILD_ARCH_BITS=32
DEB_BUILD_ARCH_CPU=arm
DEB_BUILD_ARCH_ENDIAN=little
DEB_BUILD_ARCH_LIBC=gnu
DEB_BUILD_ARCH_OS=linux
DEB_BUILD_GNU_CPU=arm
DEB_BUILD_GNU_SYSTEM=linux-gnueabihf
DEB_BUILD_GNU_TYPE=arm-linux-gnueabihf
DEB_BUILD_MULTIARCH=arm-linux-gnueabihf
DEB_HOST_ARCH=armhf
DEB_HOST_ARCH_ABI=eabihf
DEB_HOST_ARCH_BITS=32
DEB_HOST_ARCH_CPU=arm
DEB_HOST_ARCH_ENDIAN=little
DEB_HOST_ARCH_LIBC=gnu
DEB_HOST_ARCH_OS=linux
DEB_HOST_GNU_CPU=arm
DEB_HOST_GNU_SYSTEM=linux-gnueabihf
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf
DEB_HOST_MULTIARCH=arm-linux-gnueabihf
DEB_TARGET_ARCH=armhf
DEB_TARGET_ARCH_ABI=eabihf
DEB_TARGET_ARCH_BITS=32
DEB_TARGET_ARCH_CPU=arm
DEB_TARGET_ARCH_ENDIAN=little
DEB_TARGET_ARCH_LIBC=gnu
DEB_TARGET_ARCH_OS=linux
DEB_TARGET_GNU_CPU=arm
DEB_TARGET_GNU_SYSTEM=linux-gnueabihf
DEB_TARGET_GNU_TYPE=arm-linux-gnueabihf
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf

pi@raspberrypi1:~ $ cat /etc/os-release 
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
10

Raspbian sadly decided to break the nomenclature here and call their frankenstein ARMv6 port “armhf” while by definition armhf is actually defined (by ARM) as v7 (cortext-a* onwards) with hardfloat, thumb2 and neon…

this naming breakage is the sole reason that raspbian actually exists since raspbian switches off defined compiler flags for their “armhf” and re-builds the whole debian archive with this setup … with the result that there is no compatibility to any other official armhf port in the world (i.e. you can not just use debian or ubuntu packages in a stable way on their system)

the problem with snap packages is that they run on top of a “base snap” (core, core18, core20, core22) which is a minimal rootfs for the confinement.

these base snaps are built from packages in the ubuntu archive and only available for actual armhf architectures, so even if you would have a working snapd, you would not be able to run any snaps on such a system unless someone builds a base snap for armv6l …

1 Like
11

The whole 32 bit arm ecosystem is so confusing! I think I have armhf and eabihf confused, so I stand corrected.

12

Part of the problem is that even if you got snapd running, few if any of the armhf snaps published to the Snap Store use those compile flags.

While it would be possible to create a new architecture in the store, you’d also need to convince each developer to build for the additional architecture. And the pay-off isn’t great: it’s just adding compatibility for the original Raspberry Pi (superceded in 2015) and original Zero/Zero W (superceded in 2021). ARMv7-A was already well established when the original Raspberry Pi was released a decade ago.