Phill
Phill
@Prowling123 also, I'm yet to be convinced that the `install.sh` is a good way to get started. That comment is based on some of the questions that get asked on...
My opinion on this is unchanged. Basically, you get a much better user experience if you let PiBuilder do the work of installing Docker and Docker-compose, than any of the...
I am *reasonably* sure that there are no *actual* dependencies on `/home/pi` (rather than `$HOME`) or things like `chown pi:pi` (rather than `chown $USER:$USER`) left. There were a few in...
The answer to the ID=1000 question is that if you select a different username (eg "me" instead of "pi") in Raspberry Pi Imager, that user (ie "me") gets ID=1000. So...
Well, any of us saying "shouldn't" is true. But there are just so many **containers** that assume ID=1000 that it becomes a practical question of how to adapt them. Every...
It's probably time for a somewhat longer response to your question. First, a bit of conceptual background to set the scene. The web is full of information about processes that...
@ukkopahis the only "problem" is the containers that *do* support some form of ID environment variable but where we (IOTstack) haven't yet captured it in our templates. Those will still...
> Apparently a good way of getting the current userid is export TEST=$(id -u) > > in a dockerfile (which is not appropriate for most of this) it can be...
A first time user deploying IOTstack on a Pi where ID is not 1000 is probably not too much of a concern because it's probably safe to assume "running the...
It's not necessarily safe to chown everything in volumes to the current user. Some containers will barf if you change their ownership on them. Next point. There is no way...