[ST dev][en] ST and Libervia installable via Docker

Laura Bcogne llo at ygllo.com
Jeu 23 Oct 22:31:01 CEST 2014

On 22/10/2014 16:10, Goffi wrote:
> G'day,
> Le mercredi 22 octobre 2014, 14:55:39 Laura Bcogne a crit :
>> On 21/10/2014 09:06, Goffi wrote:
>>> I have also pushed again the images, as yesteray the Docker hub has
>>> some problems.
>>> You can do "./libervia_cont update" to be sure to have the last ones.
>> Pulling repository salutatoi/sat_pubsub
>> 2014/10/21 20:48:08 Get
>> https://index.docker.io/v1/repositories/salutatoi/sat_pubsub/images:
>> dial tcp: lookup index.docker.io on no answer from server
>> Error while updating salutatoi/sat_pubsub
> while this seems to be an error from the Docher Hub itself. Yesterday it was
> having some problems, maybe it's coming from this ?
> Why the ip is, do you use a local proxy ? And are you on Ubuntu 32
> bits ? "lscpu" can tell you that if you're unsure (in "Architecture").
> Cheers
> Goffi


I have retry to update today, successfully \o/ (I don't respond very 
early, sorry, my connection is low :-/)

I don't have a local proxy, and I'm not sure if i'm in ubuntu 32 or 64, 
but lscpu say me that :

Architecture:          i686
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 28
Stepping:              10
CPU MHz:               1000.000
BogoMIPS:              3325.00
Virtualization:        VT-x
L1d cache:             24K
L1i cache:             32K
L2 cache:              512K

And now, when I launch the script again, without the end-world update, 
It say that :

> root at Pavillon-rouge:~# ./libervia_cont.sh
> Running data container... A data container already exists (sat_data), 
> use "docker ps -a" to see it
> Running Libervia
> Launching prosody... Error, please check container or ask help on XMPP 
> MUC sat at chat.jabberfr.org
> error message: 2014/10/23 22:27:24 Error response from daemon: 
> Conflict, The name prosody is already assigned to 7f4c25a13987. You 
> have to delete (or rename) that container to be able to assign prosody 
> to a container again.
> Abandon

How can I exit this issue ?

"According to astronomy, when you wish upon a star,
     You're actually a few million years late.
                That star is dead
              Just like your dreams."

Plus d'informations sur la liste de diffusion dev