margueritepd
commented
8 years ago I am experiencing the same issue. (Numbers indicate the exit status of the last command.)
0 $ docker-compose run --rm web bundle install
Creating volume "web_bower_components" with default driver
Creating volume "web_web_bundle" with default driver
Creating volume "web_node_modules" with default driver
Creating volume "web_bower_components" with default driver
Creating volume "web_web_bundle" with default driver
Creating volume "web_node_modules" with default driver
ERROR: Conflict. The name "/web_web_run_6" is already in use by container a1fe6c7b7e76d66f2061b75a56bfc10de6b9cad0c2d500441f64ed74b7f3bc79. You have to remove (or rename) that container to be able to reuse that name.
1 $ docker run -it --rm --name web_web_run_6 ubuntu:14.04 /bin/bash
docker: Error response from daemon: Conflict. The name "/web_web_run_6" is already in use by container a1fe6c7b7e76d66f2061b75a56bfc10de6b9cad0c2d500441f64ed74b7f3bc79. You have to remove (or rename) that container to be able to reuse that name..
See 'docker run --help'.
1 $ docker ps -a | grep a1fe6
1 $ docker ps -a | grep web_web_run_6
1 $ docker rm web_web_run_6
Failed to remove container (web_web_run_6): Error response from daemon: No such container: web_web_run_6
1 $ docker rm /web_web_run_6
Failed to remove container (web_web_run_6): Error response from daemon: No such container: web_web_run_6
1 $ docker version
Client:
Version: 1.10.2
API version: 1.22
Go version: go1.6
Git commit: c3959b1
Built: Tue Feb 23 21:12:32 UTC 2016
OS/Arch: darwin/amd64
Server:
Version: 1.10.1
API version: 1.22
Go version: go1.5.3
Git commit: 9e83765
Built: Thu Feb 11 20:39:58 2016
OS/Arch: linux/amd64
0 $ docker info
Containers: 5
Running: 3
Paused: 0
Stopped: 2
Images: 104
Server Version: 1.10.1
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 205
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.1.17-boot2docker
Operating System: Boot2Docker 1.10.1 (TCL 6.4.1); master : b03e158 - Thu Feb 11 22:34:01 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.859 GiB
Name: default
ID: X2U3:ELQV:TVFG:YJDM:IE4N:JALI:FI6P:FJIT:AJUD:EDJF:3WBZ:XKRV
Debug mode (server): true
File Descriptors: 36
Goroutines: 65
System Time: 2016-03-04T14:31:07.557652022Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
provider=virtualbox
0 $ docker-compose --version
docker-compose version 1.6.2, build unknown
Doooooo0o
thaJeztah
osterman
robvelor
Output of
docker version:Output of
docker info:Provide additional environment details (AWS, VirtualBox, physical, etc.): Physical server, and my uname : 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.5-1~bpo8+1 (2015-11-02) x86_64 GNU/Linux
List the steps to reproduce the issue:
It's kind of random
Describe the results you received:
Describe the results you expected:
Have my container up
Additional info:
On a crashed container, it occurs that sometimes the restart is not possible anymore, neither the deletion of the so called already existing container having this name.