unable to access '/ dev / binder': No such file or directory #20

nikatshun · 2019-05-15T10:39:13Z

hello, trouble on the last command.
$ sudo modprobe ashmem_linux
$ sudo modprobe binder_linux
$ lsmod | grep -e ashmem_linux -e binder_linux
binder_linux 151552 0
ashmem_linux 20480 0
$ ls -alh /dev/binder /dev/ashmem
ls: unable to access '/ dev / binder': No such file or directory
crw------- 1 root root 10, 54 мая 15 12:33 /dev/ashmem

ubuntu 19.4

KenSharp · 2019-07-01T12:30:04Z

Are you using the anbox modules or the upstream modules?

Hattshire · 2019-07-13T04:49:50Z

Did you installed the udev files?
udev is what makes the nodes on /dev, not the driver itself, the driver/kernel just touches /sys on module load

leela-popos · 2019-09-15T09:50:20Z

I am using anbox madules and I already had the udev files, still I have same issue.

leela@pop-os:~$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem

aproposnix · 2019-10-03T07:52:37Z

I get the same error.

$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem

I'm on Ubuntu 18.04 running the 5.0.0-29-generic kernel

zaeima · 2019-10-29T11:19:44Z

I got the same issue. I am using KDE neon user edition, which is using the 5.0.0-32-generic kernel.

I have tried both installing the anbox-modules from the morphis/anbox-support PPA, and manually compiling and installing them from the instructions in this git repository. Both times, ls -alh /dev/binder /dev/ashmem and ls -1 /dev/{ashmem,binder} return the error ls: cannot access '/dev/binder': No such file or directory.

However, when I do lsmod | grep -e ashmem_linux -e binder_linux, the binder_linux module shows up. But when I attempt to run the anbox application manager, it loads for a while before crashing.

muelli · 2019-10-31T21:15:18Z

same here on a stock ubuntu 19.10, i.e. using the stock kernel.

KBeDevel · 2019-11-01T01:59:10Z

Did you check the logs with journalctl -xe?

I've found these outputs:

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:1: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:2: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

systemd-modules-load[26813]: Failed to insert module 'ashmem_linux': Operation not permitted

systemd-modules-load[26813]: Failed to insert module 'binder_linux': Operation not permitted

systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE

systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

systemd[1]: Failed to start Load Kernel Modules.

And these:

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:1:

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:2:

systemd-modules-load[26813]: Failed to insert module 'ashmem>

systemd-modules-load[26813]: Failed to insert module 'binder>

systemd[1]: systemd-modules-load.service: Main process exite>

I'm using Fedora 30 with Linux 5.3.7-200.fc30.x86_64

thomasesr · 2019-11-10T21:45:21Z

I'm heaving the same issue:

$ sudo ls -alh /dev/binder /dev/ashmem
ls: não foi possível acessar '/dev/binder': Arquivo ou diretório inexistente
crw------- 1 root root 10, 54 nov 10 18:32 /dev/ashmem
$ /dev$ sudo lsmod | grep -e ashmem_linux -e binder_linux
binder_linux          163840  0
ashmem_linux           20480  0

$ tail -n 80 /var/log/syslog
Nov 10 18:27:40 pop-os systemd[1]: Condition check resulted in Anbox Container Manager being skipped.
Nov 10 18:27:53 pop-os anbox: Failed to start as either binder or ashmem kernel drivers are not loaded
Nov 10 18:28:43 pop-os anbox: Application manager service is not running yet
Nov 10 18:30:42 pop-os systemd-resolved[888]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Nov 10 18:30:42 pop-os systemd-resolved[888]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.]
Nov 10 18:32:12 pop-os kernel: [ 6625.664667] ashmem_linux: module is from the staging directory, the quality is unknown, you have been warned.
Nov 10 18:32:12 pop-os kernel: [ 6625.665460] ashmem: initialized
Nov 10 18:32:39 pop-os anbox: Failed to start as either binder or ashmem kernel drivers are not loaded
Nov 10 18:33:29 pop-os anbox: Application manager service is not running yet
Nov 10 18:35:46 pop-os kernel: [ 6839.102257] EDAC amd64: Node 0: DRAM ECC disabled.
Nov 10 18:35:46 pop-os kernel: [ 6839.102259] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Nov 10 18:35:46 pop-os kernel: [ 6839.102259]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Nov 10 18:35:46 pop-os kernel: [ 6839.102259]  (Note that use of the override may cause unknown side effects.)
Nov 10 18:35:46 pop-os systemd-udevd[530]: /usr/lib/udev/rules.d/99-anbox.rules:1: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
Nov 10 18:35:46 pop-os systemd-udevd[530]: /usr/lib/udev/rules.d/99-anbox.rules:2: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
Nov 10 18:35:46 pop-os systemd[1]: systemd-modules-load.service: Succeeded.
Nov 10 18:35:46 pop-os systemd[1]: Stopped Load Kernel Modules.
Nov 10 18:35:46 pop-os systemd[1]: Stopping Load Kernel Modules...
Nov 10 18:35:46 pop-os systemd[1]: Starting Load Kernel Modules...
Nov 10 18:35:46 pop-os systemd[1]: Started Load Kernel Modules.
Nov 10 18:36:23 pop-os kernel: [ 6876.808101] EDAC amd64: Node 0: DRAM ECC disabled.
Nov 10 18:36:23 pop-os kernel: [ 6876.808104] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Nov 10 18:36:23 pop-os kernel: [ 6876.808104]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Nov 10 18:36:23 pop-os kernel: [ 6876.808104]  (Note that use of the override may cause unknown side effects.)
Nov 10 18:36:23 pop-os systemd-udevd[530]: /usr/lib/udev/rules.d/99-anbox.rules:1: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
Nov 10 18:36:23 pop-os systemd-udevd[530]: /usr/lib/udev/rules.d/99-anbox.rules:2: NAME="%k" is ignored, because it breaks kernel supplied names; please remove
Nov 10 18:36:24 pop-os systemd[1]: systemd-modules-load.service: Succeeded.
Nov 10 18:36:24 pop-os systemd[1]: Stopped Load Kernel Modules.
Nov 10 18:36:24 pop-os systemd[1]: Stopping Load Kernel Modules...
Nov 10 18:36:24 pop-os systemd[1]: Starting Load Kernel Modules...
Nov 10 18:36:24 pop-os systemd[1]: Started Load Kernel Modules.
Nov 10 18:37:08 pop-os anbox: Failed to start as either binder or ashmem kernel drivers are not loaded
Nov 10 18:37:59 pop-os anbox: Application manager service is not running yet

joaoapel · 2019-11-27T00:16:33Z

Same error here, on Ubuntu 19.10

yashaswi-nayak · 2019-12-08T08:20:49Z

Same issue here, using PopOS 19.10

JamesSwift · 2019-12-13T11:08:30Z

Same on PopOS 19.10

JamesSwift · 2019-12-13T11:21:45Z

This bug report seems relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493

roydenyates · 2019-12-13T23:40:59Z

This bug report seems relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493

Ubuntu 19.10. I believe not - in 19.10, the modules are compiled with the generic kernel, so the driver is present as a module. With modprobe it starts to load (it shows up in lsmod) but udev (?) fails to make the /dev/binder node. There is nothing shown in dmesg (but there is for ashmem). Symptomatically, you cannot "modprobe -r binder_linux" (ashmem with /dev/ashmem created removes just fine), likely because the hiccup with /dev/binder.

"udevadm monitor" whilst modprobing ashmem_linux and binder_linux:

KERNEL[162.221939] add      /module/ashmem_linux (module)
KERNEL[162.222025] add      /kernel/slab/:0000312 (slab)
KERNEL[162.222707] add      /devices/virtual/misc/ashmem (misc)
UDEV  [162.226862] add      /module/ashmem_linux (module)
UDEV  [162.227994] add      /kernel/slab/:0000312 (slab)
UDEV  [162.229571] add      /devices/virtual/misc/ashmem (misc)

KERNEL[183.088246] add      /module/binder_linux (module)
UDEV  [183.089557] add      /module/binder_linux (module)

Obviously very different outcomes. Bug in kernel module?

KenSharp · 2019-12-14T14:39:55Z

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:1: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:2: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

The cause has already been identified. No need to keep guessing.

JamesSwift · 2019-12-14T16:02:26Z

Great. If the cause is known, is there a way for the users to temporarily fix it? The project seems to be pretty inactive at the moment.

roydenyates · 2019-12-14T16:19:10Z

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:1: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:2: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

The cause has already been identified. No need to keep guessing.

I don't get the point - the (upstream i.e mainline) module binder_linux does not load properly to create /dev/binder. That's true without anbox installed and thus that udev rule.

justinslatten · 2019-12-17T21:29:11Z

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:1: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

systemd-udevd[568]: /usr/lib/udev/rules.d/99-anbox.rules:2: NAME="%k" is ignored, because it breaks kernel supplied names; please remove

The cause has already been identified. No need to keep guessing.

This doesn't appear to be the cause of this problem. I believe this is just a warning message. I supplied static name and still running into issue with binder.

Any idea what this is about?

Dec 17 13:23:02 localhost kernel: [279949.620827] EDAC amd64: Node 0: DRAM ECC disabled.
Dec 17 13:23:02 localhost kernel: [279949.620828] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Dec 17 13:23:02 localhost kernel: [279949.620828] Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
Dec 17 13:23:02 localhost kernel: [279949.620828] (Note that use of the override may cause unknown side effects.)

PanosChristopoulos · 2020-01-02T12:51:50Z

Have the same problem. Do we have a solution yet?

morphis · 2020-01-02T13:17:05Z

The binder driver in Ubuntu 19.10 doesn't create /dev/binder when loaded. That is intentional. Instead it provides support for binderfs (see https://brauner.github.io/2019/01/09/android-binderfs.html) which will be used instead once anbox/anbox#1309 is merged. Closing as not a bug.

auspex · 2020-01-27T15:37:58Z

How is this NOT a bug? The Anbox site tells us we don't need to install the Binder kernel module, because it's already installed. And, in fact, I couldn't anyway because you didn't have sources for 19.10. So, unless there's a workaround, I can't have anbox on a 19.10 system.

Disctanger · 2020-02-09T02:04:50Z

I have installed anbox snap and anbox modules to Fedora kernel 5.3.18-2.surface.fc31.x86_64 (currently running this kernel)

I am also having similar problem as author of this post:

$ ls -alh /dev/binder /dev/ashmem
ls: unable to access '/ dev / binder': No such file or directory

after reboot i am using $ sudo modprobe binder_linux to attach binder_linux

Then i am having the following result:
$ ls -1 /dev/{ashmem,binder} /dev/ashmem /dev/binder

If i run anbox I am seeing the following errors(?)

I am thinking my issue is also related to this post.
Would be wonderful if we could get more info about how to fix binder problem.
Currently cannot use anbox.

swd543 · 2020-04-27T14:15:10Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

koalyorg · 2020-04-28T11:30:17Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

sajedulsakib001 · 2020-04-30T09:45:45Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

will it work without binder??????

koalyorg · 2020-04-30T09:49:44Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

will it work without binder??????

If you are on Ubuntu 20.04 you won't need to install (and start) it, because it is installed (see #20 (comment))

sajedulsakib001 · 2020-04-30T16:01:39Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

will it work without binder??????

If you are on Ubuntu 20.04 you won't need to install (and start) it, because it is installed (see #20 (comment))

but sir i am also getting the same error

sajedul@Lenovo-B40-80:$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem
sajedul@Lenovo-B40-80:$

should i run anbox install command???

koalyorg · 2020-04-30T17:58:26Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

will it work without binder??????

If you are on Ubuntu 20.04 you won't need to install (and start) it, because it is installed (see #20 (comment))

but sir i am also getting the same error

sajedul@Lenovo-B40-80:~~$ ls -1 /dev/{ashmem,binder} ls: cannot access '/dev/binder': No such file or directory /dev/ashmem sajedul@Lenovo-B40-80:~~$

should i run anbox install command???

It would be enough to test ashmem, because binder doesn't exists in that place anymore. Probably you would have to start ashmem, if that doesn't work you might have to disable secure boot in bios/uefi (note that this is not ideal, see anbox/anbox#1070 ).

shamallah · 2020-05-17T08:12:03Z

I have the same issue on Ubuntu 20.04
root@vic:~# ls -1 /dev/{ashmem,binder} /dev/ashmem /dev/binder
ls: cannot access '/dev/binder': No such file or directory
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem
/dev/ashmem

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

will it work without binder??????

If you are on Ubuntu 20.04 you won't need to install (and start) it, because it is installed (see #20 (comment))

but sir i am also getting the same error
sajedul@Lenovo-B40-80:~~$ ls -1 /dev/{ashmem,binder} ls: cannot access '/dev/binder': No such file or directory /dev/ashmem sajedul@Lenovo-B40-80:~~$
should i run anbox install command???

It would be enough to test ashmem, because binder doesn't exists in that place anymore. Probably you would have to start ashmem, if that doesn't work you might have to disable secure boot in bios/uefi (note that this is not ideal, see anbox/anbox#1070 ).

Sproggy · 2020-06-05T21:25:15Z

i am using Xubuntu 20.04, i had the same issue with Anbox until i followed koalyorg's advice

run

sudo snap install --edge --devmode anbox

then run

sudo modprobe ashmem_linux

thima2017 · 2020-06-22T23:14:13Z

The both snap versions segfault on my system (Lubuntu 20.04)

this is what beta version shows:

$ snap run anbox session-manager
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
/usr/share/libdrm/amdgpu.ids: No such file or directory
[ 2020-06-22 23:05:52] [client.cpp:49@start] Failed to start container: Failed to start container: Failed to start container
[ 2020-06-22 23:05:52] [session_manager.cpp:148@operator()] Lost connection to container manager, terminating.
[ 2020-06-22 23:05:53] [daemon.cpp:61@Run] Container is not running
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Stack trace (most recent call last) in thread 6660:
#8    Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in 
#7    Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f3e9feb241c, in clone
#6    Object "/lib/x86_64-linux-gnu/libpthread.so.0", at 0x7f3ea19646b9, in 
#5    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f3ea0443d37, in 
#4    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f3ea0418700, in std::terminate()
#3    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f3ea04186b5, in 
#2    Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f3ea041a84c, in __gnu_cxx::__verbose_terminate_handler()
#1    Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f3e9fde2029, in abort
#0    Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f3e9fde0428, in gsignal
Aborted (Signal sent by tkill() 6474 1000)
Aborted (core dumped)

@morphis

wording taken from anbox/anbox-modules#20 (comment) @morphis comment ref anbox#20 anbox#1309 anbox#1240

ntzxtyz · 2020-07-22T10:48:26Z

The same error here on Ubuntu 20.04,

thima2017 · 2020-07-22T12:52:55Z

Bugreport on launchpad https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1884810

Screwitfix · 2020-08-17T19:17:18Z

Same issue with Ubuntu 20.04. You dont seem to support the newer versions of ubuntu so better put it in the docs.

Anbox works fine with Ubuntu 20.04. Installed it via snap (edge) and done sudo modprobe ashmem_linux.

the snap version is not installing & the repository version has a bug that is no bug and get no fix = anbox is unusable

ondbyte · 2020-10-04T15:30:56Z

this can be resolved, take look at, this

krzydoug · 2020-10-06T21:40:13Z

this can be resolved, take look at, this

I can confirm this finally got my anbox working again, THANK YOU!

zachlai · 2020-12-31T07:36:30Z

I tried this way, and solved this issue.
see:
https://superuser.com/questions/1590707/ls-cannot-access-dev-binder-no-such-file-or-directory-in-anbox

thexcryptocompany · 2021-02-07T09:19:27Z

I'm using the latest version of pop os but the above link does'nt help me in any way do i need to install snap??? or something??? else

kunalrustagi08 · 2021-02-13T13:31:06Z

I'm using the latest version of pop os but the above link does'nt help me in any way do i need to install snap??? or something??? else

I installed snap on pop os for installing anbox, but I am getting the error ls: cannot access '/dev/binder': No such file or directory.

Any luck?

ondbyte · 2021-02-13T18:11:05Z

I'm using the latest version of pop os but the above link does'nt help me in any way do i need to install snap??? or something??? else

I installed snap on pop os for installing anbox, but I am getting the error ls: cannot access '/dev/binder': No such file or directory.

Any luck?

This thread addresses the exact problem in your question, check the answers mentioned above

alfredousan · 2021-06-12T23:27:28Z

I tried this way, and solved this issue.
see:
https://superuser.com/questions/1590707/ls-cannot-access-dev-binder-no-such-file-or-directory-in-anbox

unfortunately that didn't work for me either way

alfredousan · 2021-06-12T23:29:11Z

The binder driver in Ubuntu 19.10 doesn't create /dev/binder when loaded. That is intentional. Instead it provides support for binderfs (see https://brauner.github.io/2019/01/09/android-binderfs.html) which will be used instead once anbox/anbox#1309 is merged. Closing as not a bug.

is there a workaround to use this software without using bindings, by chance? this seems too difficult to troubleshoot! thanks for your attention :)

Hattshire · 2021-06-13T20:21:31Z

The correcto way of doing it is by using udev, but if you would like to drop a bash script to do it, you can have one like ``` #/bin/sh mkdir /dev/binder mount -t binderfs /dev/binder ``` execute it using systemd on boot, or every so with crontab and it should work, however, it's kinda sketchy and the udev way is far more simple an elegant.

revdeluxe · 2021-11-22T05:07:09Z

How is this NOT a bug? The Anbox site tells us we don't need to install the Binder kernel module, because it's already installed. And, in fact, I couldn't anyway because you didn't have sources for 19.10. So, unless there's a workaround, I can't have anbox on a 19.10 system.

It's a Dependencies issue. that's because your OS didn't met the build requirements...

zeankundev · 2021-12-03T05:58:15Z

Same thing here on Ubuntu 20.04

zeankundev@zeankundev-ThinkPad-T510:~/anbox-modules$ ./INSTALL.sh
[sudo] password for zeankundev: 

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.11.0-27-generic all KERNEL_SRC=/lib/modules/5.11.0-27-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for anbox-ashmem: 1 not found
Error! Bad return status for module build on kernel: 5.11.0-27-generic (x86_64)
Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.11.0-27-generic all KERNEL_SRC=/lib/modules/5.11.0-27-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for anbox-binder: 1 not found
Error! Bad return status for module build on kernel: 5.11.0-27-generic (x86_64)
Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
binder_linux          196608  0
ashmem_linux           20480  0
ls: cannot access '/dev/binder': No such file or directory
crw------- 1 root root 10, 122 Des  3 12:54 /dev/ashmem

JaisonJose241 · 2022-08-28T19:23:21Z

any update on this?

sukanenen · 2022-10-29T03:16:37Z

i am using Xubuntu 20.04, i had the same issue with Anbox until i followed koalyorg's advice

run

sudo snap install --edge --devmode anbox

then run

sudo modprobe ashmem_linux

work for me ty .. i use linux mint 21 cinnamon

morphis closed this as completed Jan 2, 2020

roydenyates mentioned this issue Jan 2, 2020

ls: cannot access '/dev/binder': No such file or directory #42

Closed

CaioF mentioned this issue Apr 6, 2020

ls: cannot access '/dev/binder': No such file or directory anbox/anbox#1387

Closed

paulvi added a commit to paulvi/anbox that referenced this issue Jun 30, 2020

Update docs for unable to access '/ dev / binder'

674508b

wording taken from anbox/anbox-modules#20 (comment) @morphis comment ref anbox#20 anbox#1309 anbox#1240

paulvi mentioned this issue Jun 30, 2020

Update docs for unable to access '/ dev / binder' anbox/anbox#1520

Merged

leandrokemp mentioned this issue Sep 5, 2021

Cannot compile... anbox/anbox#1828

Open

unable to access '/ dev / binder': No such file or directory #20

unable to access '/ dev / binder': No such file or directory #20

Comments

nikatshun commented May 15, 2019 • edited

KenSharp commented Jul 1, 2019

Hattshire commented Jul 13, 2019

leela-popos commented Sep 15, 2019

aproposnix commented Oct 3, 2019

zaeima commented Oct 29, 2019

muelli commented Oct 31, 2019

KBeDevel commented Nov 1, 2019

thomasesr commented Nov 10, 2019

joaoapel commented Nov 27, 2019

yashaswi-nayak commented Dec 8, 2019

JamesSwift commented Dec 13, 2019

JamesSwift commented Dec 13, 2019

roydenyates commented Dec 13, 2019 • edited

KenSharp commented Dec 14, 2019 • edited

JamesSwift commented Dec 14, 2019

roydenyates commented Dec 14, 2019 • edited

justinslatten commented Dec 17, 2019

PanosChristopoulos commented Jan 2, 2020

morphis commented Jan 2, 2020

auspex commented Jan 27, 2020

Disctanger commented Feb 9, 2020 • edited

swd543 commented Apr 27, 2020

koalyorg commented Apr 28, 2020

sajedulsakib001 commented Apr 30, 2020

koalyorg commented Apr 30, 2020

sajedulsakib001 commented Apr 30, 2020 • edited

koalyorg commented Apr 30, 2020 • edited

shamallah commented May 17, 2020

Sproggy commented Jun 5, 2020

thima2017 commented Jun 22, 2020 • edited

ntzxtyz commented Jul 22, 2020

thima2017 commented Jul 22, 2020

Screwitfix commented Aug 17, 2020

ondbyte commented Oct 4, 2020 • edited

krzydoug commented Oct 6, 2020

zachlai commented Dec 31, 2020

thexcryptocompany commented Feb 7, 2021

kunalrustagi08 commented Feb 13, 2021

ondbyte commented Feb 13, 2021 • edited

alfredousan commented Jun 12, 2021

alfredousan commented Jun 12, 2021

Hattshire commented Jun 13, 2021 via email • edited

revdeluxe commented Nov 22, 2021

zeankundev commented Dec 3, 2021

JaisonJose241 commented Aug 28, 2022

sukanenen commented Oct 29, 2022 • edited

nikatshun commented May 15, 2019 •

edited

roydenyates commented Dec 13, 2019 •

edited

KenSharp commented Dec 14, 2019 •

edited

roydenyates commented Dec 14, 2019 •

edited

Disctanger commented Feb 9, 2020 •

edited

sajedulsakib001 commented Apr 30, 2020 •

edited

koalyorg commented Apr 30, 2020 •

edited

thima2017 commented Jun 22, 2020 •

edited

ondbyte commented Oct 4, 2020 •

edited

ondbyte commented Feb 13, 2021 •

edited

Hattshire commented Jun 13, 2021 via email •

edited

sukanenen commented Oct 29, 2022 •

edited