golang April 2014

golang@lists.fedoraproject.org

7 participants
400 discussions

[Bug 1035304] New: Error when starting a container: cannot unmarshal bool into Go value of type string
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1035304 Bug ID: 1035304 Summary: Error when starting a container: cannot unmarshal bool into Go value of type string Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mgoldman(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, vbatts(a)redhat.com Description of problem: accept4(7, 0xc2001be540, [112], SOCK_CLOEXEC|SOCK_NONBLOCK) = -1 EAGAIN (Resource temporarily unavailable) read(9, "POST /v1.7/containers/create HTT"..., 4096) = 550 clock_gettime(CLOCK_REALTIME, {1385557957, 704016349}) = 0 clock_gettime(CLOCK_REALTIME, {1385557957, 704076878}) = 0 clock_gettime(CLOCK_REALTIME, {1385557957, 704218620}) = 0 write(2, "[debug] api.go:1008 Calling POST"..., 52[debug] api.go:1008 Calling POST /containers/create ) = 52 futex(0xd0bef8, FUTEX_WAIT, 0, NULL2013/11/27 14:12:37 POST /v1.7/containers/create [/var/lib/docker|237066b1] +job create() [/var/lib/docker|237066b1] -job create() = ERR (ExportEnv json: cannot unmarshal bool into Go value of type string) [error] api.go:1034 Error: create: ExportEnv json: cannot unmarshal bool into Go value of type string [error] api.go:82 HTTP Error: statusCode=500 create: ExportEnv json: cannot unmarshal bool into Go value of type string [debug] api.go:1008 Calling GET /images/json 2013/11/27 14:28:41 GET /v1.7/images/json This issue exists when running docker-io-0.7.0-2.el6.x86_64 (unreleased) as daemon with following flag: -b none. [root@centos64 ~]# docker -v Docker version 0.7.0, build 0d078b6/0.7.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1037634] New: The devicemapper volumes are not removed after container is removed
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1037634 Bug ID: 1037634 Summary: The devicemapper volumes are not removed after container is removed Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mfojtik(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: After removing all containers in Docker, some of the devicemapper volumes are not removed and they are showed in 'df -h' Version-Release number of selected component (if applicable): [root@localhost postgresql]# docker -v Docker version 0.7.0, build 0ff9bc1/0.7.0 How reproducible: Create some containers and then use 'docker rm CONTAINER_ID' and remove them all. When the list of all containers (docker ps -a), is empty, run 'df -h'. There are some devicemapper volumes from removed container still mounted in system. After restarting docker service they seems to be properly removed. Steps to Reproduce: 1. docker run ... (create some containers) 2. docker rm ALL_CONTAINERS 3. df -h (-> will show several devicemapper volumes mounted) 4. systemctl restart docker 5. df -h (-> all devicemapper volumes are erased) Actual results: [root@localhost postgresql]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [root@localhost postgresql]# [root@localhost postgresql]# df -h | grep mapper /dev/mapper/fedora-root 9.2G 5.0G 3.7G 58% / /dev/dm-3 9.8G 390M 8.9G 5% /var/lib/docker/devicemapper/mnt/64e0619c473e974ac710568673fa0907fe9bc78f6998888ff41913cf6a69af0b /dev/dm-4 9.8G 388M 8.9G 5% /var/lib/docker/devicemapper/mnt/1bdd590de956281c7a5b1394cc0801ee879bc220be52e399eb61a9c3f2810c0d /dev/dm-5 9.8G 235M 9.0G 3% /var/lib/docker/devicemapper/mnt/97fc5bf7f8d42606fa896e1d391a0b882f78322ce0ff77c03fbd7f8e3b7a73ed /dev/dm-6 9.8G 388M 8.9G 5% /var/lib/docker/devicemapper/mnt/a567e6f3d26a5736d00a5e9be9a609b44ab13f0e43fc466f45beaa7ea9054766 /dev/mapper/docker-253:1-15108-7ee96a4f5167932745b68de0d026d750d12afa911a0e2591edd48efebdc8eb2f-init 9.8G 390M 8.9G 5% /var/lib/docker/devicemapper/mnt/7ee96a4f5167932745b68de0d026d750d12afa911a0e2591edd48efebdc8eb2f-init /dev/mapper/docker-253:1-15108-c8c302f735e607c55ac4ae542fda9081959f128abbe3b126fa9afa541c84d52d-init 9.8G 518M 8.7G 6% /var/lib/docker/devicemapper/mnt/c8c302f735e607c55ac4ae542fda9081959f128abbe3b126fa9afa541c84d52d-init /dev/mapper/docker-253:1-15108-5d0694e3a73324e395adfd03d7524c76f126c7449a4f5b73bac64b7bf26f51ef-init 9.8G 556M 8.7G 6% /var/lib/docker/devicemapper/mnt/5d0694e3a73324e395adfd03d7524c76f126c7449a4f5b73bac64b7bf26f51ef-init /dev/mapper/docker-253:1-15108-f8a7e54667e09c1e9f3edf104124279d2e34fa1bade1ccbd8772a85369132cb6-init 9.8G 591M 8.7G 7% /var/lib/docker/devicemapper/mnt/f8a7e54667e09c1e9f3edf104124279d2e34fa1bade1ccbd8772a85369132cb6-init /dev/mapper/docker-253:1-15108-fcf2d918ff47b9f24b1a9dcd6ea2829d4b20a5736f06d0a6d987c5cce74d4a55-init 9.8G 591M 8.7G 7% /var/lib/docker/devicemapper/mnt/fcf2d918ff47b9f24b1a9dcd6ea2829d4b20a5736f06d0a6d987c5cce74d4a55-init /dev/mapper/docker-253:1-15108-004e09e25c19d765db7c75a767fffead530cac52aefd82d6acec5a9e765d4149-init 9.8G 591M 8.7G 7% /var/lib/docker/devicemapper/mnt/004e09e25c19d765db7c75a767fffead530cac52aefd82d6acec5a9e765d4149-init /dev/mapper/docker-253:1-15108-5f32ced8736080d768cf72f210cda8ae06ef23d7018e5f07819c4c59607ae488-init 9.8G 591M 8.7G 7% /var/lib/docker/devicemapper/mnt/5f32ced8736080d768cf72f210cda8ae06ef23d7018e5f07819c4c59607ae488-init -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1037830] New: Error pulling image, Authentication is required / Server error: 404
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1037830 Bug ID: 1037830 Summary: Error pulling image, Authentication is required / Server error: 404 Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: jeckersb(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: Version-Release number of selected component (if applicable): docker-io-0.7.0-14.el6.x86_64 Red Hat Enterprise Linux Server release 6.5 (Santiago) How reproducible: Always Steps to Reproduce: 1. Run `docker -d -b none -D` 2. In another terminal, run `docker pull mattdm/fedora` Actual results: # docker pull mattdm/fedora Pulling repository mattdm/fedora 1bdd590de956: Error pulling image (f20) from mattdm/fedora, Authentication is required. 64e0619c473e: Error pulling image (latest) from mattdm/fedora, Authentication is required. 97fc5bf7f8d4: Error pulling image (f20rc3.small) from mattdm/fedora, Authentication is required. a567e6f3d26a: Error pulling image (f19) from mattdm/fedora, Authentication is required. 2013/12/03 21:15:36 Server error: 404 trying to fetch remote history for mattdm/fedora Expected results: (Taken from my F20 system which works perfectly) # docker pull mattdm/fedora Pulling repository mattdm/fedora 1bdd590de956: Download complete a567e6f3d26a: Download complete 64e0619c473e: Download complete 97fc5bf7f8d4: Download complete Additional info: There doesn't seem to be anything useful in the daemon output by default. I've added debug statements in various places to try and understand what's going on. I'll elaborate in future comments when I can better organize what I'm seeing. Just wanted to get this out there incase it's something obvious :) -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1038329] New: Updating docker-io should probably restart the daemon
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1038329 Bug ID: 1038329 Summary: Updating docker-io should probably restart the daemon Product: Fedora Version: 19 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: luto(a)mit.edu QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com I upgraded docker-io and, after the upgrade, I got errors about missing dockerinit. systemctl restart docker fixed it. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1045173] New: Accessing Docker containers from outside network - adding firewall exceptions problem
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1045173 Bug ID: 1045173 Summary: Accessing Docker containers from outside network - adding firewall exceptions problem Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ajinkya(a)ajinkyakulkarni.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com I am using Docker 0.7.0 to create containers on RedHat Enterprise Linux 6.5. When firewall is turned off containers can talk to outside world, but when firewall is on, container cannot be accessed from outside. This is how I am running the docker and mapping a port from host to container $ docker run -i -t -p 3838:3838 shiny "shiny-server" Without firewall, I can access Node.js server running inside a container on port 3838 from outside network as http://servername:3838, but not with firewall turned on. These are my default firewall rules – ============================================== # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT ============================================== I have tried opening a port 3838 by adding a rule as below, but it does not work -A INPUT -m state --state NEW -m tcp -p tcp --dport 3838 -j ACCEPT Docker is creating a virtual NAT on the host machine, I am feeling that somehow firewall is blocking the packet forwarding from eth0 to docker 0 This is the output of $ifconfig (I have masked the server IP) docker0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::87d:8dff:fed0:f16d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:408321 errors:0 dropped:0 overruns:0 frame:0 TX packets:681809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:126511933 (120.6 MiB) TX bytes:924200959 (881.3 MiB) eth0 Link encap:Ethernet HWaddr 00:25:64:A8:5B:8F inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:255.255.240.0 inet6 addr: XXXX::XXX:XXXX:XXXX:XXXX/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29786186 errors:0 dropped:0 overruns:0 frame:0 TX packets:1137982 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4209047011 (3.9 GiB) TX bytes:234657696 (223.7 MiB) Interrupt:17 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8444 errors:0 dropped:0 overruns:0 frame:0 TX packets:8444 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4701771 (4.4 MiB) TX bytes:4701771 (4.4 MiB) Output of $docker version : Client version: 0.7.0 Go version (client): go1.1.2 Git commit (client): 0ff9bc1/0.7.0 Server version: 0.7.0 Git commit (server): 0ff9bc1/0.7.0 Go version (server): go1.1.2 Last stable version: 0.7.2, please update docker Output of $docker info: Containers: 321 Images: 278 Driver: devicemapper Pool Name: docker-8:17-13239310-pool Data file: /var/lib/docker/devicemapper/devicemapper/data Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata Data Space Used: 56464.5 Mb Data Space Total: 102400.0 Mb Metadata Space Used: 59.5 Mb Metadata Space Total: 2048.0 Mb I need help in making docker containers accessible from outside network without turning off the entire firewall. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1071896] New: Fedora base image update failure in trusted builds at Docker index
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1071896 Bug ID: 1071896 Summary: Fedora base image update failure in trusted builds at Docker index Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: nshaikh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: I am using trusted build feature of Docker index and using Dockerfile [1] to build an image at Docker index. Dockerfile[1] is using stackbrew/fedora as base image. I am running "yum -y update" command in Dockerfile, however update is failing for systemd.x86_64 0:208-9.fc20 , check logs here[2]. I have retried building the image at Docker index, however each time it is failing with same error. Logs for 4 builds:[3] [1] https://github.com/swordphilic/redis-fedora/blob/master/Dockerfile [2] https://index.docker.io/builds/github/2159/swordphilic/redis-fedora/builds/… [3] https://index.docker.io/builds/github/2159/swordphilic/redis-fedora/builds -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1088828] New: specifying tty crashes docker
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1088828 Bug ID: 1088828 Summary: specifying tty crashes docker Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: nmavrogi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: Running docker as: sudo docker run -P --tty=false -p 22 -p 5551:5551/udp -a stderr -n --name test test1 works. However changing --tty=false to --tty=true brings the following backtrace: panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x20 pc=0x4f8d1d] goroutine 7 [running]: runtime.panic(0x8a5ac0, 0x1149948) /usr/lib64/golang/src/pkg/runtime/panic.c:266 +0xb6 bufio.(*Reader).writeBuf(0xc210038a80, 0x0, 0x0, 0x90aea0, 0x7f5c00000001, ...) /usr/lib64/golang/src/pkg/bufio/bufio.go:430 +0x6d bufio.(*Reader).WriteTo(0xc210038a80, 0x0, 0x0, 0x7f5cf5b40258, 0x0, ...) /usr/lib64/golang/src/pkg/bufio/bufio.go:402 +0x4d io.Copy(0x0, 0x0, 0x7f5cf5b40130, 0xc210038a80, 0x0, ...) /usr/lib64/golang/src/pkg/io/io.go:344 +0xa5 github.com/dotcloud/docker/api.func·016(0x0, 0x0) /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/api/client.go:2279 +0xf8 github.com/dotcloud/docker/utils.func·002() /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/utils/utils.go:38 +0x2e created by github.com/dotcloud/docker/utils.Go /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/utils/utils.go:39 +0xa7 goroutine 1 [runnable]: net/http.ReadResponse(0xc210038cc0, 0xc2100b1680, 0xc2100b1680, 0xc210050950, 0xc210000d01) /usr/lib64/golang/src/pkg/net/http/response.go:108 +0x3b net/http/httputil.(*ClientConn).Read(0xc2100b0420, 0xc2100b1680, 0x0, 0x0, 0x0) /usr/lib64/golang/src/pkg/net/http/httputil/persist.go:397 +0x37b net/http/httputil.(*ClientConn).Do(0xc2100b0420, 0xc2100b1680, 0x0, 0x0, 0x0) /usr/lib64/golang/src/pkg/net/http/httputil/persist.go:421 +0x85 github.com/dotcloud/docker/api.(*DockerCli).call(0xc2100468c0, 0x935500, 0x4, 0xc210038c00, 0x52, ...) /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/api/client.go:2119 +0x86b github.com/dotcloud/docker/api.(*DockerCli).CmdRun(0xc2100468c0, 0xc21000a020, 0xc, 0xc, 0x0, ...) /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/api/client.go:1924 +0x17d9 reflect.callMethod(0xc2100ac060, 0x7f5cf59aeab8) /usr/lib64/golang/src/pkg/reflect/value.go:676 +0x17b reflect.methodValueCall(0xc21000a020, 0xc, 0xc, 0xc2100ac060, 0x7f5cf5b3e101) /usr/lib64/golang/src/pkg/reflect/asm_amd64.s:26 +0x24 github.com/dotcloud/docker/api.ParseCommands(0xc2100ad020, 0x4, 0xc2100ad027, 0x14, 0xc21000a010, ...) /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/api/client.go:70 +0x31f main.main() /builddir/build/BUILD/docker-0.9.1/docker/docker.go:151 +0x1f5f goroutine 3 [syscall]: os/signal.loop() /usr/lib64/golang/src/pkg/os/signal/signal_unix.go:21 +0x1e created by os/signal.init·1 /usr/lib64/golang/src/pkg/os/signal/signal_unix.go:27 +0x31 goroutine 6 [chan receive]: github.com/dotcloud/docker/api.(*DockerCli).hijack(0xc2100468c0, 0x935500, 0x4, 0xc2100b90e0, 0x65, ...) /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/api/client.go:2307 +0x98a github.com/dotcloud/docker/api.func·011(0x0, 0x6964c0) /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/api/client.go:1902 +0x1be github.com/dotcloud/docker/utils.func·002() /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/utils/utils.go:38 +0x2e created by github.com/dotcloud/docker/utils.Go /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/utils/utils.go:39 +0xa7 goroutine 8 [runnable]: github.com/dotcloud/docker/utils.func·002() /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/utils/utils.go:37 created by github.com/dotcloud/docker/utils.Go /builddir/build/BUILD/docker-0.9.1/_build/src/github.com/dotcloud/docker/utils/utils.go:39 +0xa7 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1041400] New: docker permission denied errors
by Red Hat Bugzilla 22 May '14

22 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1041400 Bug ID: 1041400 Summary: docker permission denied errors Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: rest api calls seem to fail for docker on rawhide Version-Release number of selected component (if applicable): 0.7.1 (both rpm and binary released by upstream) How reproducible: consistent Steps to Reproduce: 1. install docker-io (via yum or upstream binary) 2. try 'docker search' / 'docker pull' / 'docker login' or anything else Actual results: $ sudo docker search fedora 2013/12/12 09:43:53 Error: Get https://index.docker.io/v1/search?q=fedora: dial tcp 54.234.135.251:443: permission denied Expected results: should show a list of fedora images Additional info: I didn't find this in f19 or epel (only on rawhide) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1057340] New: rpm macros for golang
by Red Hat Bugzilla 21 May '14

21 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1057340 Bug ID: 1057340 Summary: rpm macros for golang Product: Fedora Version: rawhide Component: golang Severity: low Assignee: adam(a)spicenitz.org Reporter: vbatts(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, skottler(a)redhat.com, vbatts(a)redhat.com include in the golang rpm an /etc/rpm/macros.golang for defining %gopath such that it is a system definition. There may be other rpm automations to add as well. Ideally a post script for __spec_install_post that could produce Provides: and Requires: of the golang() libraries exported and imported. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1071605] New: sshd not working in fedora image
by Red Hat Bugzilla 15 May '14

15 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1071605 Bug ID: 1071605 Summary: sshd not working in fedora image Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: pantinor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, skottler(a)redhat.com, vbatts(a)redhat.com Description of problem: Running sshd on a fresh docker fedora image fails with this error: Failed to get D-Bus connection: No connection to service manager. Version-Release number of selected component (if applicable): $ docker -v Docker version 0.8.0, build cc3a8c8/0.8.0 $ docker inspect fedora [{ "id": "58394af373423902a1b97f209a31e3777932d9321ef10e64feaaa7b4df609cf9", "parent": "8abc22fbb04266308ff408ca61cb8f6f4244a59308f7efc64e54b08b496c58db", "created": "2014-02-03T16:10:40.500814677Z", "container": "f718f19a28a5147da49313c54620306243734bafa63c76942ef6f8c4b4113bc5", "container_config": { "Hostname": "88807319f25e", "Domainname": "", "User": "", "Memory": 0, "MemorySwap": 0, "CpuShares": 0, "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "PortSpecs": null, "ExposedPorts": null, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "HOME=/", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ], "Cmd": [ "/bin/sh", "-c", "#(nop) ADD fedora-20-medium.tar.xz in /" ], "Dns": null, "Image": "8abc22fbb04266308ff408ca61cb8f6f4244a59308f7efc64e54b08b496c58db", "Volumes": null, "VolumesFrom": "", "WorkingDir": "", "Entrypoint": null, "NetworkDisabled": false, "OnBuild": null }, "docker_version": "0.6.3", "author": "Lokesh Mandvekar \u003clsm5(a)redhat.com\u003e - ./buildcontainers.sh", "config": { "Hostname": "88807319f25e", "Domainname": "", "User": "", "Memory": 0, "MemorySwap": 0, "CpuShares": 0, "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "PortSpecs": null, "ExposedPorts": null, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "HOME=/", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ], "Cmd": null, "Dns": null, "Image": "8abc22fbb04266308ff408ca61cb8f6f4244a59308f7efc64e54b08b496c58db", "Volumes": null, "VolumesFrom": "", "WorkingDir": "", "Entrypoint": null, "NetworkDisabled": false, "OnBuild": null }, "architecture": "x86_64", "Size": 385520098 }] How reproducible: Always Steps to Reproduce: 1. docker run -t -i fedora bash 2. bash-4.2# yum install -y openssh-server 3. bash-4.2# systemctl start sshd Actual results: Failed to get D-Bus connection: No connection to service manager. bash-4.2# service sshd status Redirecting to /bin/systemctl status sshd.service Failed to get D-Bus connection: No connection to service manager. Expected results: A running sshd daemon Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

← Newer
1
2
3
4
5
6
7
...
40
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang April 2014