distrobox.conf causes distroboxes to not launch after latest system update
I have a ublue-fedora-distrobox one and bazzite-arch one, and I just updated my system, and both are now saying this instead of launching:
This is what I have in my distrobox.conf
If I remove it they launch but now I can't set trillium-next data folder.
This used to work before update
12 Replies
what does the flag do and why you require it
it makes my trillium store my notes in that path that I specified
do you need to set it in distrobox conf? why not set it from your rc file
I just picked the first path that I could find in my system from there https://github.com/89luca89/distrobox?tab=readme-ov-file#configure-distrobox but I will try moving it into the ${HOME}/.distroboxrc one
GitHub
GitHub - 89luca89/distrobox: Use any linux distribution inside your...
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available...
not distroboxrc, but your bashrc or zshrc
or maybe .profile
oh I tried but it caused an error
I don't remember what it was
I just couldn't find how to do it
try again and post the error
also which application need this?
I think I remember that there was no error and I added this to end of bashrc
export VARNAME="my value" and it just didn't work
but I will try again
triliumnext-binif it doesnt work try
/etc/environment
put TRILIUM_DATA_DIR=/var/mnt/ssd/Notes/Trilium without export
also i saw it have docker, usually its better to run that compared to distroboxwouldn't that disable itself after reboot because its immutable?
I think docker is more heavy but I haven't looked into it
its like a full os
after update probably, but not reboot
distrobox should be more heavier, they use the same tech underneath but distrobox have more integration
nice i think it worked
you know what happened
i accidentally pasted
export VARNAME="my value" instead of TRILIUM_DATA_DIR=/var/mnt/ssd/Notes/Trilium
but i also did something else which fixed it but i dont remeber what it was so so if anyone has the same issue idk how to fix it
I just added export C_INCLUDE_PATH="~/miniconda3/envs/pytorch312/bin/nvcc" to my bashrc and it didnt fix my issue that I was having so I am going to remember what it was
i have no idea why trilium works because I removed the trilium data dir from both bashrc and stupid distrobox.conf
the container_manager_additional_flags='--env C_INCLUDE_PATH=/home/jj/distrobox/fedora/miniconda3/envs/pytorch312/bin/nvcc' still doesn't work
moving it into the ${HOME}/.distroboxrc one doesnt fix it either
turns out it was pytorch issue
so this solution does actually work but somehow without using it trilium got fixed in some other way too