Skip to content
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

symbolic links from /linuxrc -> /bin/busybox in host filesystem breaks many applications #494

Closed
jyelloz opened this issue Jan 18, 2017 · 1 comment

Comments

@jyelloz
Copy link

jyelloz commented Jan 18, 2017

I was trying to run org.gnome.Builder and org.gnome.gitg in flatpak 0.8.1 and encountered the failure:

flatpak run org.gnome.gitg
Can't create file at /bin/busybox: Read-only file system

It turns out I had a symbolic link at /linuxrc that pointed to /bin/busybox. Once I removed /linuxrc things worked normally.

I have tested putting a symbolic link with any filename (such as /testfile, /abc, etc.) in my host filesystem root and pointing it to /bin/busybox will cause the same failure. Pointing any link in the host FS root directory to something like /bin/ls or /bin/yes doesn't seem to break things, though.

@jyelloz
Copy link
Author

jyelloz commented Jan 18, 2017

I've applied the patch from #495 against flatpak 0.8.1 and it works for me.

alexlarsson added a commit that referenced this issue Jan 19, 2017
For instance like in #494
if there is a /linuxrc -> /bin/busybox symlink, and /bin/busybox
is not in the runtime then we will fail creating it as a mountpoint
for the bind mount.

Fixes #494

(cherry picked from commit 592bea2)
matthiasclasen pushed a commit to matthiasclasen/flatpak that referenced this issue Feb 21, 2017
For instance like in flatpak#494
if there is a /linuxrc -> /bin/busybox symlink, and /bin/busybox
is not in the runtime then we will fail creating it as a mountpoint
for the bind mount.

Fixes flatpak#494
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant