John
John
May not be a perfect solution, but I got around the issue of redirects by handling the 301 inside a custom fetch resolver and returning a new $ref from it...
Possibly related to #416 but not entirely sure.
I'm getting the same issue as above. Even after reboot aplay -l isn't showing the device. ``` dkms is already the newest version (2.3-2). git is already the newest version...
``` pi@raspberrypi:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA] Subdevices: 7/7 Subdevice #0: subdevice #0 Subdevice...
> exactly same issue with kernel `4.19.109-v7+` on raspberry 3b+ I was getting an error further up the install script about the kernel version not being found. I got around...
Just a followup, I get a similar issue if I use the `transformRef` property, even if the `baseUri` is only 1 level deep: ``` const resolver = new Resolver({ transformRef:...
Did anyone solve this? I found a few images on Dockerhub for arm64 - but they're not the latest version. Building locally on my RPi5 fails consistently.