33 Replies
I'm sure there's a simple explaination, I just don't understand distrobox all that well yet
I also don't know why
.cargo
.config
.profile
, and .rustup
are root owned, but it seems to be related
and bash
also does not have this issue. Only fish for some reason
Hey @tulip, you seen this error before?seems like selinux is being really mad at you
Oh huh
But it's in my home dir?
try doing
find . -maxdepth 1 > myfiles.txt
on your host and on your distrobox
then run delta myfiles.txt myfiles-on-distrobox.txt
brew install git-delta
you'll see what its so mad aboutWhat's that do?
gets all your files as a list and saves it to a file
then you can compare which ones show up and which ones dont
the missing ones on the distrobox file list is what is getting permission denied
oooooh
@Raevenant

something is wrong on ur fish config
Stack Overflow
Fish Shell: "error: Unable to open universal variable file '/': Per...
I am using the Fish shell (version 3.3.1) on MacOS. Every time I run a command it shows this error multiple times:
error: Unable to open universal variable file '/': Permission denied
The commands
try clearing it up
then re-add stuff and see what breaks it
Hmmmmm
But it happens I think because the config is root
Like, fish works fine if I remove the init_hooks bit
also highly recommend not putting this stuff on init_hooks
Oh
What instead?
try making a custom distrobox image with boxkit
Oh 😂
then put a Justfile in
/usr/share/yourthing/Justfile
and some alias for it or something
myboxjust
then BAM you have the same functionality its just "optional"Honestly that works for me lmao a few of the things I want to add need like, API keys n stuff
i think the thing is that the init_hooks part is being run as root on the container and its making it so your regular user bound to the container doesnt get read access to the fish config
Yuuuuuup
or dunno
I'll give this a shot and get back to you 😄
just know you cant modify
/home
on the containerfileGitHub
GitHub - tulilirockz/treats: My distroboxes for personal development
My distroboxes for personal development. Contribute to tulilirockz/treats development by creating an account on GitHub.
was testing out some stuff so its all broken but there you go
meaning I would still need to do a
distrobox assemble create
with a modification to the home?youd need to do something like putting a justfile in /usr or /etc on the container
its better than doing it via an init_hook
but its manual, as in you need to run
just -f /etc/Justfile
to get ur stuff for exampleI'm confused
running that inside the container?
or as in using
just
to build the image?
just
is like make
right?just
whenever you are running the distrobox
like on ur host
not on the container buildoh would this replace the normal distrobox commands?
i.e. the terminal wouldn't have a dropdown for it?
i guess you can just put like a script on your
$HOME
and do whatever you wanna do?
it would be like:
oh gotcha. I went through your repo, and it makes sense to me
how would you handle needing an API key or secrets in your image deployment?
i think the same way you'd do that with any other docker image
github secrets and maybe a private registry?
I was a little distracted when I was asking this all before, buy why is it not recommended to do init_hook stuff?
(I'm still going to do the custom image approach I think) It looks cleaner