You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by "Woods, Darren L" <dw...@alamo.edu> on 2022/06/23 17:23:13 UTC
Guacamole Docker Install Error
I'm getting this error message when I run the command:
sudo docker run --name some-guacd -d -p 4822:4822 guacamole/guacd
docker: Error response from daemon: Conflict. The container name "/some-guacd" is already in use by container "8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
Thanks,
Darren Woods
Re: Guacamole Docker Install Error
Posted by Michael Jumper <mj...@apache.org>.
On Thu, Jun 23, 2022 at 10:23 AM Woods, Darren L <dw...@alamo.edu> wrote:
> I’m getting this error message when I run the command:
>
> sudo docker run --name some-guacd -d -p 4822:4822 guacamole/guacd
>
>
>
> docker: Error response from daemon: Conflict. The container name
> "/some-guacd" is already in use by container
> "8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e". You
> have to remove (or rename) that container to be able to reuse that name.
>
> See 'docker run --help'.
>
Yes. This means that the container name "/some-guacd" is already in use by
container
"8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e". You
have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
- Mike
Re: Guacamole Docker Install Error
Posted by Lee Doughty <le...@virginiacyberrange.org>.
This is really a docker question, this fails before guacamole even has a
chance to start. I only mention this because the expertise here on this
guacamole mailing list might only by chance include docker skills, so you
might not get the *most correct* answers
In short, that error message clearly indicates there's a naming conflict.
You can get this conflict in docker if you rename containers (I've seen
this exact error message when renaming a docker-compose container without
destroying the old one).
I can't tell you WHY it thinks great_solomon is some-guacd, I'd expect the
container IDs to match, that's where I point to my previous statement: "we
are not a docker mailing list". If you want that answer, you'd need to go
to them.
If you just want a solution, I expect this would work:
`docker system prune` (to go nuclear)
or
`docker container prune` (which should work if no containers are running)
In the future, I recommend you ALWAYS use the "--rm" (remove) flag with
`docker run`, this will remove the container when done.
If you want to keep the container between sessions, then you need to use
`docker start|stop` after the run command, and you'll need to `docker rm`
containers manually when you want to `docker run` a new one.
Hope this helps.
-Lee
On Thu, Jun 23, 2022 at 7:08 PM Ivanmarcus <iv...@yahoo.com.invalid>
wrote:
> Darren,
>
> I'm far from a Docker expert but that command string looks corrupted
> from where I'm sitting?
>
> As I see it the system believes there's a container running with the
> same name you're trying to run, and it's giving the container ID.
>
> You can use 'docker images' to check that out (ie. that you have such a
> container), and from there'd I use 'docker ps' followed by 'docker
> inspect [container ID]' in order to look into things further.
>
> If it were me I'd close any containers you have running presently, then
> just start the one you want first and check that's ok before carrying on
> with an others. Given the questionmark (to me) from your output I think
> that's warranted...
>
> Aside from the specific issue you have I found that Docker took a while
> to get my hear around it, and as with many things computer some of the
> commands were a bit cryptic, or didn't do exactly what I expected. I'm
> still not that au fait with it, but some reading of multiple information
> sources usually helps me through :-)
>
> On 24/06/22 06:42, Woods, Darren L wrote:
> > sudo docker container list -all
> >
> > CONTAINER ID IMAGE COMMAND CREATED
> > STATUS PORTS NAMES
> >
> > 51b04782c0f9 guacamole/guacd "/bin/sh -c '/usr/lo…" 2 hours
> > ago Up 2 hours (healthy) 4822/tcp great_solomon
> >
> > I don’t see that container named some-guacd.
> >
> > Darren
> >
> > *From:* Nick Couchman <vn...@apache.org>
> > *Sent:* Thursday, June 23, 2022 12:41 PM
> > *To:* user@guacamole.apache.org
> > *Subject:* Re: Guacamole Docker Install Error
> >
> > **THIS EMAIL IS FROM AN EXTERNAL SENDER OUTSIDE OF THE ALAMO COLLEGES.
> > Be cautious before clicking links or opening attachments from unknown
> > sources. Do not provide personal or confidential information.**
> >
> > On Thu, Jun 23, 2022 at 1:23 PM Woods, Darren L <dwoods3@alamo.edu
> > <ma...@alamo.edu>> wrote:
> >
> > I’m getting this error message when I run the command:
> >
> > sudo docker run --name some-guacd -d -p 4822:4822 guacamole/guacd
> >
> > docker: Error response from daemon: Conflict. The container name
> > "/some-guacd" is already in use by container
> > "8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e".
> > You have to remove (or rename) that container to be able to reuse
> > that name.
> >
> > See 'docker run --help'.
> >
> > Try "docker container list --all" and see if you see the container
> > already called "some-guacd".
> >
> > -Nick
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
>
>
Re: Guacamole Docker Install Error
Posted by Ivanmarcus <iv...@yahoo.com.INVALID>.
Darren,
I'm far from a Docker expert but that command string looks corrupted
from where I'm sitting?
As I see it the system believes there's a container running with the
same name you're trying to run, and it's giving the container ID.
You can use 'docker images' to check that out (ie. that you have such a
container), and from there'd I use 'docker ps' followed by 'docker
inspect [container ID]' in order to look into things further.
If it were me I'd close any containers you have running presently, then
just start the one you want first and check that's ok before carrying on
with an others. Given the questionmark (to me) from your output I think
that's warranted...
Aside from the specific issue you have I found that Docker took a while
to get my hear around it, and as with many things computer some of the
commands were a bit cryptic, or didn't do exactly what I expected. I'm
still not that au fait with it, but some reading of multiple information
sources usually helps me through :-)
On 24/06/22 06:42, Woods, Darren L wrote:
> sudo docker container list -all
>
> CONTAINER ID IMAGE COMMAND CREATED
> STATUS PORTS NAMES
>
> 51b04782c0f9 guacamole/guacd "/bin/sh -c '/usr/lo…" 2 hours
> ago Up 2 hours (healthy) 4822/tcp great_solomon
>
> I don’t see that container named some-guacd.
>
> Darren
>
> *From:* Nick Couchman <vn...@apache.org>
> *Sent:* Thursday, June 23, 2022 12:41 PM
> *To:* user@guacamole.apache.org
> *Subject:* Re: Guacamole Docker Install Error
>
> **THIS EMAIL IS FROM AN EXTERNAL SENDER OUTSIDE OF THE ALAMO COLLEGES.
> Be cautious before clicking links or opening attachments from unknown
> sources. Do not provide personal or confidential information.**
>
> On Thu, Jun 23, 2022 at 1:23 PM Woods, Darren L <dwoods3@alamo.edu
> <ma...@alamo.edu>> wrote:
>
> I’m getting this error message when I run the command:
>
> sudo docker run --name some-guacd -d -p 4822:4822 guacamole/guacd
>
> docker: Error response from daemon: Conflict. The container name
> "/some-guacd" is already in use by container
> "8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e".
> You have to remove (or rename) that container to be able to reuse
> that name.
>
> See 'docker run --help'.
>
> Try "docker container list --all" and see if you see the container
> already called "some-guacd".
>
> -Nick
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
RE: Guacamole Docker Install Error
Posted by "Woods, Darren L" <dw...@alamo.edu>.
sudo docker container list -all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
51b04782c0f9 guacamole/guacd "/bin/sh -c '/usr/lo…" 2 hours ago Up 2 hours (healthy) 4822/tcp great_solomon
I don’t see that container named some-guacd.
Darren
From: Nick Couchman <vn...@apache.org>
Sent: Thursday, June 23, 2022 12:41 PM
To: user@guacamole.apache.org
Subject: Re: Guacamole Docker Install Error
**THIS EMAIL IS FROM AN EXTERNAL SENDER OUTSIDE OF THE ALAMO COLLEGES.
Be cautious before clicking links or opening attachments from unknown sources. Do not provide personal or confidential information.**
On Thu, Jun 23, 2022 at 1:23 PM Woods, Darren L <dw...@alamo.edu>> wrote:
I’m getting this error message when I run the command:
sudo docker run --name some-guacd -d -p 4822:4822 guacamole/guacd
docker: Error response from daemon: Conflict. The container name "/some-guacd" is already in use by container "8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
Try "docker container list --all" and see if you see the container already called "some-guacd".
-Nick
Re: Guacamole Docker Install Error
Posted by Nick Couchman <vn...@apache.org>.
On Thu, Jun 23, 2022 at 1:23 PM Woods, Darren L <dw...@alamo.edu> wrote:
> I’m getting this error message when I run the command:
>
> sudo docker run --name some-guacd -d -p 4822:4822 guacamole/guacd
>
>
>
> docker: Error response from daemon: Conflict. The container name
> "/some-guacd" is already in use by container
> "8062906e4e1eaee1e1433043042ce349201da78eef0f6e5d893d6c9956ca1f8e". You
> have to remove (or rename) that container to be able to reuse that name.
>
> See 'docker run --help'.
>
>
>
Try "docker container list --all" and see if you see the container already
called "some-guacd".
-Nick
>