coreboot-builder-scripts VS docker

Have you tried building just coreboot for the w541 yet? I would suggest doing that if you haven't. I need to update it, but this what I used. Due to flaky connections to the chromebook images, I sourced the mrc.bin from skulls. This is the proper way to do it.

You can Skull's build scripts are based on my coreboot-builder-scripts, which does rely on x86 Docker. You can build on coreboot on an RPi but you need to compile crossgcc. I have not done this myself in sometime and the only tutorial I know if the Karl Cordes's x220 tutoial. While the dependencies are outdated the crossgcc build command is likely the same.

I finally got it! Long story short, I used the coreboot-sdk docker image for the toolchain through the great coreboot-builder-scripts repository (it needs a couple adjustments that I've detailed in this other thread: OpenBSD in Thinkpad x220 with Coreboot 4.7.

We can use the https://github.com/Thrilleratplay/coreboot-builder-scripts to use the coreboot-sdk toolchain and compile Coreboot 4.7, however we need to make a couple of adjustments:

Docker images can be built and/or pulled from a repository like hub.docker.com. Here is the link to coreboot-sdk but would suggest looking at other Docker images like the official NextCloud image to get a better sense of how standalone Docker image applications can be configured. If you want a better idea of how to use the coreboot-sdk, I use it in my coreboot-builder-scripts

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).

If you look at the info on https://hub.docker.com/_/nextcloud, you'll see that you aught to be specifying at least one volume, so that you have the data you want to not disappear on restart, and can access config files.

Yes, and this is what L passed through as the env variables in the docker compose file, as the docs state: https://hub.docker.com/_/nextcloud

You can't map binaries from host to container like this. What you need is a custom Dockerfile that installs ffmpeg. https://github.com/nextcloud/docker/blob/master/.examples/dockerfiles/full/fpm/Dockerfile

A good example to start with is at https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/insecure/postgres/apache

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