Certbot-snap and processor 32bits

Hello,
Certbot-auto will no longer be supported.
I have a Raspberry PI4 whose processor is ARMv7 Processor rev 3 (v7l) in 32bits.
I am using Apache and Raspbian GNU/Linux 10 (buster)

I therefore cannot use as a replacement: Snap Support
Certbot snap supports requires x86_64, ARMv7. (I am in 32 bits).

What can I use instead? (Do you have a link with the procedure to follow?)

Thank you so much

1 Like

Hi @Yodul

if you have such an old system, may be acme.sh works.

Check the list of clients:

You're mixing up processor architectures: ARM is very much distinct from x86 and AMD64 (a.k.a. x86_64).

While there are indeed 32 and 64 bit ARM architectures, I'm pretty sure your RPi 4 is 64 bit. I myself own a RPi 4B which has the same identity as yours "ARMv7 Processor rev 3 (v7l)" and is identified in /proc/cpuinfo as part of the BCM2711 SoC. And the BCM2711 SoC contains a 64 bits ARM A72 core. Also note that there are no RPi 4Bs with another SoC than the BCM2711.

You can also use dpkg --print-architecture to see the architecture you need to select @ Snap, which is armhf in my case.

2 Likes

I don't understand the complaint.

My Pi4 shows:
uname -a

Linux raspberrypi 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux

And it can:
sudo apt install snapd
sudo snap install core
sudo snap refresh core
sudo snap install certbot --classic
/snap/bin/certbot --version
returns:
certbot 1.10.1

NOTE: If you have installed snap [apt install snap], you will have to install+refresh the snap core.
[don't install snap - install snapd]

2 Likes

Hello Osiris,

I looked on my PI4B
He gives me this:
cat cpuinfo

processor: 0
model name: ARMv7 Processor rev 3 (v7l)
BogoMIPS: 135.00
Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x0
CPU part: 0xd08
CPU revision: 3

processor: 1
model name: ARMv7 Processor rev 3 (v7l)
BogoMIPS: 135.00
Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x0
CPU part: 0xd08
CPU revision: 3

processor: 2
model name: ARMv7 Processor rev 3 (v7l)
BogoMIPS: 135.00
Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x0
CPU part: 0xd08
CPU revision: 3

processor: 3
model name: ARMv7 Processor rev 3 (v7l)
BogoMIPS: 135.00
Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x0
CPU part: 0xd08
CPU revision: 3

Hardware: BCM2835
Revision: b03111
Serial: 100000002e1143f4
Model: Raspberry Pi 4 Model B Rev 1.1

dpkg --print-architecture
armhf

It's strange in Hardware BCM2835 !!!

Thank you very much for the information, the PI4B is 64bits. It reassures me.

I don't understand what use is it knowing it's armhf to use snap?

Thanks for your help

1 Like

So you have "proof" it's fully supported:

(The i386 entry is a relic from the past by the way which ironically isn't supported. If you'd select that, you'd see an old version of certbot for only the "edge" channel. The certbot team still needs to remove that.)

It is kinda strange your Pi identifies the SoC as the BCM2835 indeed. However, your CPU implementer, architecture, variant, part and revision are the same as my BCM2711. I have the same model with the same revision listed in cpuinfo as you.

Ah, found it: see the " Why does cpuinfo report I have a BCM2835?" entry at Raspberry Pi Documentation It seems I need to upgrade my kernel :stuck_out_tongue:

2 Likes

NICE!
Mine is only 108.00

2 Likes

I've got 180 :sunglasses:

4 Likes

Mine is only a sticky mess on a flaky crust that goes well with whipped cream. :slightly_frowning_face:

2 Likes

You’ve got it good, mine is fried in amps. Though I do think it would be good with whipped cream....

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.