docker, arch, and beaglebone black

[cswank]

Based on reading this issue tracker:
https://github.com/dotcloud/docker/issues/636
I am under the impression that I should be able to install arch (I installed the latest this morning) on my beaglebone black and get docker working out of the box. I tried the following after installing docker with packman::
$this->bbcode_second_pass_code('', '[root@alarm tmp]# docker import http://archlinuxarm.org/os/ArchLinuxARM … est.tar.gz archbase
Downloading from http://archlinuxarm.org/os/ArchLinuxARM … est.tar.gz
b292df94485143e8417f827a8d89c80f17504d0fa34e051e388484d010b04515
[root@alarm tmp]# ===========================================>] 179.4 MB/179.4 MB
[root@alarm tmp]#
[root@alarm tmp]#
[root@alarm tmp]# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
archbase latest b292df944851 3 minutes ago 378.1 MB
[root@alarm tmp]# docker run -i -t archbase /bin/bash
2014/05/12 16:59:05 Error: Cannot start container 6f0ce084b89d2664f60f251a85285148695127989c0fcb882f65480dbe52aa78: mountpoint not found')
It doesn't work. Does anyone have any insight?

[WarheadsSE]

Immediately, by thoughts go to some issue with the kernel, or file systems. Confirm which kernel modules are loaded, and please also configure docker to use the -D (debug) flag so that we can get more detail out of journalctl.

[cswank]

lsmod looks the same before and after doing 'modprobe auks' I'm not sure if that means anything.

Also, I edited /etc/systemd/system/multi-user.target.wants/docker.service to pass in the -D arg. I found the error at the end of journalctl but it looks the same as what I posted originally:

2014/05/12 16:59:05 Error: Cannot start container 6f0ce084b89d2664f60f251a85285148695127989c0fcb882f65480dbe52aa78: mountpoint not found

$this->bbcode_second_pass_code('', '[root@alarm multi-user.target.wants]# lsmod
Module Size Used by
xt_addrtype 2417 2
xt_conntrack 2748 1
iptable_filter 1485 1
ipt_MASQUERADE 1713 1
iptable_nat 2489 1
nf_conntrack_ipv4 13159 2
nf_defrag_ipv4 1366 1 nf_conntrack_ipv4
nf_nat_ipv4 3511 1 iptable_nat
nf_nat 16195 3 ipt_MASQUERADE,nf_nat_ipv4,iptable_nat
nf_conntrack 79868 6 ipt_MASQUERADE,nf_nat,nf_nat_ipv4,xt_conntrack,iptable_nat,nf_conntrack_ipv4
ip_tables 10929 2 iptable_filter,iptable_nat
x_tables 16868 5 ip_tables,ipt_MASQUERADE,xt_conntrack,iptable_filter,xt_addrtype
bridge 79985 0
stp 2036 1 bridge
llc 5527 2 stp,bridge
autofs4 21976 2 ')


Does this help?

[cswank]

Here is all the output from journalctl after a failed 'docker run -i -t archbase /bin/bash':

$this->bbcode_second_pass_code('', 'May 13 07:08:56 alarm docker[507]: [debug] server.go:988 Calling POST /containers/create
May 13 07:08:58 alarm docker[507]: 2014/05/13 07:08:56 POST /v1.11/containers/create
May 13 07:08:58 alarm docker[507]: [3924ea66] +job create()
May 13 07:08:58 alarm docker[507]: [error] mount.go:11 [warning]: couldn't run auplink before unmount: exec: "auplink": executable file not found in $PATH
May 13 07:08:58 alarm docker[507]: [3924ea66] -job create() = OK (0)
May 13 07:08:58 alarm docker[507]: [debug] server.go:988 Calling POST /containers/{name:.*}/attach
May 13 07:08:58 alarm docker[507]: 2014/05/13 07:08:58 POST /v1.11/containers/7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5/attach?stderr=1&stdin=1&stdout=1&stream=1
May 13 07:08:58 alarm docker[507]: [3924ea66] +job inspect(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5, container)
May 13 07:08:58 alarm docker[507]: [3924ea66] -job inspect(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5, container) = OK (0)
May 13 07:08:58 alarm docker[507]: [3924ea66] +job attach(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5)
May 13 07:08:58 alarm docker[507]: [debug] attach.go:22 attach: stdin: begin
May 13 07:08:58 alarm docker[507]: [debug] attach.go:59 attach: stdout: begin
May 13 07:08:58 alarm docker[507]: [debug] attach.go:97 attach: stderr: begin
May 13 07:08:58 alarm docker[507]: [debug] attach.go:143 attach: waiting for job 1/3
May 13 07:08:58 alarm docker[507]: [debug] server.go:988 Calling POST /containers/{name:.*}/start
May 13 07:08:58 alarm docker[507]: 2014/05/13 07:08:58 POST /v1.11/containers/7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5/start
May 13 07:08:58 alarm docker[507]: [3924ea66] +job start(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5)
May 13 07:08:58 alarm docker[507]: [3924ea66] +job allocate_interface(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5)
May 13 07:08:58 alarm docker[507]: [3924ea66] -job allocate_interface(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5) = OK (0)
May 13 07:08:59 alarm docker[507]: [error] container.go:455 Error running container: mountpoint not found
May 13 07:08:59 alarm docker[507]: [3924ea66] +job release_interface(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5)
May 13 07:08:59 alarm docker[507]: [3924ea66] -job release_interface(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5) = OK (0)
May 13 07:08:59 alarm docker[507]: [error] container.go:512 7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5: Error closing terminal: invalid argument
May 13 07:08:59 alarm docker[507]: [error] mount.go:11 [warning]: couldn't run auplink before unmount: exec: "auplink": executable file not found in $PATH
May 13 07:08:59 alarm docker[507]: [debug] attach.go:76 attach: stdout: end
May 13 07:08:59 alarm docker[507]: [debug] attach.go:114 attach: stderr: end
May 13 07:08:59 alarm docker[507]: [debug] attach.go:148 attach: job 1 completed successfully
May 13 07:08:59 alarm docker[507]: [debug] attach.go:143 attach: waiting for job 2/3
May 13 07:08:59 alarm docker[507]: [debug] attach.go:148 attach: job 2 completed successfully
May 13 07:08:59 alarm docker[507]: [debug] attach.go:143 attach: waiting for job 3/3
May 13 07:08:59 alarm docker[507]: [debug] attach.go:49 attach: stdin: end
May 13 07:08:59 alarm docker[507]: [debug] attach.go:148 attach: job 3 completed successfully
May 13 07:08:59 alarm docker[507]: [debug] attach.go:150 attach: all jobs completed successfully
May 13 07:08:59 alarm docker[507]: [3924ea66] -job attach(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5) = OK (0)
May 13 07:08:59 alarm docker[507]: [debug] server.go:2361 Closing buffered stdin pipe
May 13 07:08:59 alarm docker[507]: [3924ea66] +job release_interface(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5)
May 13 07:08:59 alarm docker[507]: [3924ea66] -job release_interface(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5) = OK (0)
May 13 07:08:59 alarm docker[507]: [error] container.go:512 7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5: Error closing terminal: invalid argument
May 13 07:08:59 alarm docker[507]: Cannot start container 7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5: mountpoint not found
May 13 07:08:59 alarm docker[507]: [3924ea66] -job start(7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5) = ERR (1)
May 13 07:08:59 alarm docker[507]: [error] server.go:1014 Error: Cannot start container 7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5: mountpoint not found
May 13 07:08:59 alarm docker[507]: [error] server.go:90 HTTP Error: statusCode=500 Cannot start container 7191dfa74f55cecfda368a7196893818723e9d6ec3e014de648749e4c51a72d5: mountpoint not found')

[WarheadsSE]

Saw this, think I have seen it other places, without issue.
$this->bbcode_second_pass_quote('', '
')May 13 07:08:59 alarm docker[507]: [error] mount.go:11 [warning]: couldn't run auplink before unmount: exec: "auplink": executable file not found in $PATH

[cswank]

I have seen references to auplink as well as I'm researching this and have found a few people say it is safe to ignore that error.

[cswank]

shouldn't aufs show up in the lsmod results that I posted?

[WarheadsSE]

Which kernel do you have installed?

I installed linux-am33x, rebooted.
$this->bbcode_second_pass_code('', '
[root@bbbc ~]# pacman -S docker lxc
[root@bbbc ~]# systemctl start docker
[root@bbbc ~]# cat ArchLinuxARM-armv7-latest.tar.gz | docker import - alarm/armv7:latest
[root@bbbc ~]# docker run -i -t alarm/armv7 /bin/bash
[root@e150b924dcd6 /]#
')

[cswank]

You dog! I just can't wait to get docker working on my BBB's.

I'm pretty sure I loaded this one:
http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz

from the instructions at:
http://archlinuxarm.org/platforms/armv7 ... bone-black

I'm going repeat the install one more time and docker import the same exact container you did.

[WarheadsSE]

The image, by default comes with linux-am33x-legacy, which is the "official" but not mainlined "bone" kernel. There might be some issues with it.