-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to enter toolbox container #5
Comments
This resolves cgwalters#5
I get the same error on regular Fedora 30 on master (a583a3e). |
This resolves cgwalters#5
@matyasselmeci does #6 work for you? I rebased it on the recent changes to master, and it still fixes my issue. |
No, there is no change for me. I am not running OSTree, just vanilla Fedora 30 Workstation. |
This resolves cgwalters#5
@cgwalters first... thanks for this project. Inspired me to start learning rust, and to run silverblue as my main OS. second, any thoughts on this issue? #6 fixes it for me, but maybe there is a better way that would also fix it for @matyasselmeci |
This resolves cgwalters#5
turns out my fix was actually much simpler... I just needed to set $HOME properly. It was set to /home/trown which is a symlink to /var/home/trown. If I set HOME=/var/home/trown before creating a container with |
Cool! 👍
Hmm. Right, you generally want to do that. This is a saga though, see e.g. Probably coretoolbox should be resilient to this. |
BTW I think you want to |
I get the following error using master on fedora silverblue:
mount: /var/home/trown: special device /host/home/trown does not exist.
error: Initializing container (static): Child ["mount" "--rbind" "/host/home/trown" "/home/trown"]
If I go back to dd30b27 things work great. So it would seem there is some issue with 2542ba4
I will continue to investigate, but I thought I would post a stub in case anyone else hits this.
The text was updated successfully, but these errors were encountered: