BB vol

[docker-library]

BB vol

[tianon]

Not sure I understand -- what's your question? This looks like a list of steps you're taking to build something, and I can't really follow it (let alone derive from it what makes it related to this Docker image?)

[necrose99]

have busybox , as /bb volume/folder .. ie via Dockerhub can run commands via bb vol since emulation wont load. or update emu..
ie x86/amd64 to run a few commands , wget , while building a qemu from scratch arm/arm64 or otherwise.. and add /bb/ dir to ones containers ...

ADD BBVOL-amd64-utils to build setting to add /bb to item

/usr/bin/bash on arm64 wont run in Dockerhub... however having /bb/sh or /bb/bash
/bb/wget and a busybox as a substitute most commands will run fine..
add newer qemu , to root of container.. and other wrappers...

Gentoo thus far runs nicely as docker on native arm64 , however getting emu/qemu to run is a mother...FFFF@@@ having a drop in busybox in a volume and at /bb/
/bb/sh < load-qemu-bash.sh > @/bin/bash and or load the resin.io emulation layer etc.

other use cases , Dockerhub 5-30 seconds ... build don't go... build dies after X Seconds...
having /bb vol for more problematic builds to just keep running could allow for failsafe build.

https://github.com/gentoo/gentoo-docker-images/blob/master/build.sh via /bb/sh & wget
https://github.com/gentoo/gentoo-docker-images/blob/master/stage3.Dockerfile will run under x86 or amd64 , arm64 , arm7hf not so much..

however /bb/ as a volume /folder , could just use native cpu tools to build the fs containers in Dockerhub in automatic fashion.. /bb/bash /bb/echo to put typical host file in place etc.
and build arm/arm64 rootfs containers without fail..

/bb , for native cpu tools to build non native things or load qemu in Dockerhub etc..
and other likely useful things having busybox in a /bb folder/vol could give..

[tianon]

If you're having issues with https://github.com/gentoo/gentoo-docker-images, I suggest you take it up with them.

Unfortunately, I'm not really able to make heads or tails of what it is you're trying to explain -- I also don't see how any of it is really relevant to this repository (which is the repository for the busybox Docker image and has nothing to do with Gentoo or Bash).

[necrose99]

https://gist.github.com/necrose99/8a3f9184dbcc8d59640db078e2fdfc72

Work in progress ,
while true gentoo has know containers , (arm64 aint one...)

i have to hand build gentoo-arm64 from scratch... and can not easily let docker hub do this..
as emulation layers without privileges are irritating. hoping to fix this..
https://hub.docker.com/add/automated-build would be quite the nicety.. add busybox matching host cpu to do dirtywork @ /bb/ .... (from busybox-vol... ) /bb/sh < run my shell scripts to build the rootfs... wala simple..

taking the binary busybox /bb/busybox ... something somethin... ln -s all the apps ...
fake bash @ busybox sh or shove in /bb/bin/bash else add a static bash etc.. to /bb/bin/bash...
(from https://github.com/docker-library/busybox binary > /bb/ for bb vol )
from busybox-vol... let users have as a builder option all i had in mind.
however so simple is having busybox & symlink apps in a /bb folder for use and as a docker to pull into automated builds...

yours builds busybox
having a simple variant and as a /bb/ vol to exploit.. but no....
From (or add to autobuilds) from docker-library/busybox-tools-vol... add /bb/ and symlinks

add userland tools to /bb/ as users/use cases need too.. to own clones of the bbvol...
use native cpu busybox to shim qemu etc. if possible in dockerhub... or quay,io if not run scripts using busybox

go get txtfile if newer update rootfs image...

rm -r /bb/* @ end.. else nest builds .. then prune..