coreboot VS docker

Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.

1: https://www.coreboot.org/

Coreboot is 0.6% C++.

NovaCustom ; some models come with Dasharo a coreboot distribution.

There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.

coreboot/devicetree.cb at bcc9879151c0ff61dfa3f2206b538d5c8be619ba · coreboot/coreboot (github.com)

You usually can't take existing firmware and run it on a new CPU, because the new CPU requires different bringup code anyway. Take a look at https://github.com/coreboot/coreboot/tree/master/src/soc/int... to get some idea of how many different implementations there are for modern Intel alone (there's a bunch more for the pre-SoC style Intels). If you already have to port your firmware to a new CPU, you can deal with the CPU starting in a different mode - it is entirely an implementation detail that can be handled in the firmware.

NEM/CAR is used to avoid hacks like romcc. you need memory for a stack/etc if you want to run C code; romcc worked around this by compiling C code to asm that only used registers (no stack usage at all). this isn't needed if you can use NEM/CAR. either way I wouldn't say this massively reduces latency, since code is still being backed by SPI flash MMIO

Novacustom. Some models come with Dasharo an open source firmware based on coreboot.

It seems that Intel is currently 404ing the I remember in the 82579LM datasheet regarding firmware made a vague reference to the Intel ME being used the PXE boot. If the ME parition has neutered or the generated GBE partition is being used, this shouldn't be a concern.

Coreboot/Libreboot (recently merged with OSboot, so presumably that means the policy problems have been fixed) as far as I know do not benefit from any such standardization and often have to resort to reverse-engineering.

Am I better off using this container: https://hub.docker.com/_/nextcloud/

It looks like I'm not the only person who has faced this. apache-based images require buster, for instance, and some docker images that rely on Ruby face issues too (for example, I decided to try setting up Postal but it looks like it's facing the same issues).

Nextcloud is free and open source. The easiest way to install it is via docker containers. nextcloud docker

The correct way to do it is to build your own docker container with the command to install the smbclient installed. You can find example docker files here: https://github.com/nextcloud/docker/tree/master/.examples/dockerfiles/smb

Have you considered Docker? There is an official NextCloud image https://hub.docker.com/_/nextcloud

I just use this Dockerfile and something like this docker-compose file. The result is super-flexible (not everyone needs this though).

Some of the extensions have dependencies not included in base image. They keep the base image clean to keep it small. See some of their official examples. https://github.com/nextcloud/docker/tree/master/.examples/dockerfiles/full. I’m using their official image as the base image and adding dependencies. I based mine off of https://github.com/andrey18106/mediadc-docker-example, but use Nextcloud 25 as the latest version (25 is latest stable with most plugins up to it) as well as dependency additions for recognize and facial recognition extensions not available in base.

However, you should probably take a look at the official nextcloud all-in-one docker setup. Otherwise, the official nextcloud docker image comes preinstalled and provides lots of customization options via environment variables (like NEXTCLOUD_DATA_DIR).