From goffi at goffi.org Mon Oct 20 17:51:24 2014 From: goffi at goffi.org (Goffi) Date: Mon, 20 Oct 2014 17:51:24 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= Message-ID: <54452F7C.7040905@goffi.org> G'day, we have just published Docker images to install easily Salut à Toi and Libervia. You can download the libervia manager script and make it executable like this: $ wget http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh && chmod a+x libervia_cont.sh Then to download/launch Libervia and all its dependencies, just do (once Docker is installed): $ ./libervia_cont.sh There are facilities to run, stop, update, backup, etc. For more infomrations, check http://wiki.goffi.org/wiki/Docker/en All feedbacks welcome (including the containers and the documentation). Cheers Goffi From llo at ygllo.com Mon Oct 20 23:52:07 2014 From: llo at ygllo.com (=?windows-1252?Q?Laura_B=E9cogn=E9e?=) Date: Mon, 20 Oct 2014 23:52:07 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <54452F7C.7040905@goffi.org> References: <54452F7C.7040905@goffi.org> Message-ID: <54458407.2080001@ygllo.com> On 20/10/2014 17:51, Goffi wrote: > G'day, > > we have just published Docker images to install easily Salut à Toi and > Libervia. You can download the libervia manager script and make it > executable like this: > > $ wget > http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh > && chmod a+x libervia_cont.sh > > Then to download/launch Libervia and all its dependencies, just do > (once Docker is installed): > $ ./libervia_cont.sh > > There are facilities to run, stop, update, backup, etc. > > For more infomrations, check http://wiki.goffi.org/wiki/Docker/en > > All feedbacks welcome (including the containers and the documentation). Hello, I have try to follow the process, but outch, it end up like that when I launch the script : > d614a92cc13c: Download complete > > Download of latest salutatoi/data finished > > Running data container... OK > (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) > > Running Libervia > > Launching prosody... OK > (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) > Launching sat_pubsub... Error, please check container or ask help on > XMPP MUC sat at chat.jabberfr.org > error message: > 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d > 2014/10/20 23:47:20 Error response from daemon: Cannot start container > 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: > Cannot link to a non running container: /prosody AS /sat_pubsub/prosody > Abandon I'm in ubuntu 14 From goffi at goffi.org Tue Oct 21 08:36:58 2014 From: goffi at goffi.org (Goffi) Date: Tue, 21 Oct 2014 08:36:58 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <54458407.2080001@ygllo.com> References: <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> Message-ID: <5445FF0A.10003@goffi.org> G'day, thanks for your feedback. That's weird, why docker can't launch the container ? Can you try to launch it by hand ? You need to launch prosody before, so you need to enter: docker run -ti --rm --name prosody salutatoi/prosody docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub Before doing that, you can stop all SàT containers with ./libervia_cont.sh stop what do you have with "docker version" ? Do you have free space on your hard drives ? It happened several time to me because docker was installed on my system partition which is small... Thank you On 20/10/2014 23:52, Laura Bécognée wrote: > On 20/10/2014 17:51, Goffi wrote: >> G'day, >> >> we have just published Docker images to install easily Salut à Toi and >> Libervia. You can download the libervia manager script and make it >> executable like this: >> >> $ wget >> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >> && chmod a+x libervia_cont.sh >> >> Then to download/launch Libervia and all its dependencies, just do >> (once Docker is installed): >> $ ./libervia_cont.sh >> >> There are facilities to run, stop, update, backup, etc. >> >> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >> >> All feedbacks welcome (including the containers and the documentation). > > Hello, > > I have try to follow the process, but outch, it end up like that when I > launch the script : > >> d614a92cc13c: Download complete >> >> Download of latest salutatoi/data finished >> >> Running data container... OK >> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >> >> Running Libervia >> >> Launching prosody... OK >> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >> Launching sat_pubsub... Error, please check container or ask help on >> XMPP MUC sat at chat.jabberfr.org >> error message: >> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >> Cannot link to a non running container: /prosody AS /sat_pubsub/prosody >> Abandon > > I'm in ubuntu 14 > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From goffi at goffi.org Tue Oct 21 09:06:12 2014 From: goffi at goffi.org (Goffi) Date: Tue, 21 Oct 2014 09:06:12 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <5445FF0A.10003@goffi.org> References: <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> <5445FF0A.10003@goffi.org> Message-ID: <544605E4.4060504@goffi.org> 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. Cheers On 21/10/2014 08:36, Goffi wrote: > G'day, > > thanks for your feedback. > > That's weird, why docker can't launch the container ? Can you try to > launch it by hand ? You need to launch prosody before, so you need to > enter: > docker run -ti --rm --name prosody salutatoi/prosody > docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub > > Before doing that, you can stop all SàT containers with > ./libervia_cont.sh stop > > what do you have with "docker version" ? > > Do you have free space on your hard drives ? It happened several time to > me because docker was installed on my system partition which is small... > > Thank you > > On 20/10/2014 23:52, Laura Bécognée wrote: >> On 20/10/2014 17:51, Goffi wrote: >>> G'day, >>> >>> we have just published Docker images to install easily Salut à Toi and >>> Libervia. You can download the libervia manager script and make it >>> executable like this: >>> >>> $ wget >>> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >>> && chmod a+x libervia_cont.sh >>> >>> Then to download/launch Libervia and all its dependencies, just do >>> (once Docker is installed): >>> $ ./libervia_cont.sh >>> >>> There are facilities to run, stop, update, backup, etc. >>> >>> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >>> >>> All feedbacks welcome (including the containers and the documentation). >> >> Hello, >> >> I have try to follow the process, but outch, it end up like that when I >> launch the script : >> >>> d614a92cc13c: Download complete >>> >>> Download of latest salutatoi/data finished >>> >>> Running data container... OK >>> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >>> >>> Running Libervia >>> >>> Launching prosody... OK >>> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >>> Launching sat_pubsub... Error, please check container or ask help on >>> XMPP MUC sat at chat.jabberfr.org >>> error message: >>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >>> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >>> Cannot link to a non running container: /prosody AS /sat_pubsub/prosody >>> Abandon >> >> I'm in ubuntu 14 >> >> _______________________________________________ >> dev mailing list >> dev at goffi.org >> http://lists.goffi.org/listinfo/dev > > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From monsieurpaullebouanger at arghh.org Tue Oct 21 10:46:20 2014 From: monsieurpaullebouanger at arghh.org (MonsieurPaulLeBoulanger) Date: Tue, 21 Oct 2014 08:46:20 +0000 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: <544605E4.4060504@goffi.org> References: <544605E4.4060504@goffi.org> <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> <5445FF0A.10003@goffi.org> Message-ID: Hi, I'm experiencing the same issue, I still have this error after the update : Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) Launching sat_pubsub... Error, please check container or ask help on XMPP MUC sat at chat.jabberfr.org error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 2014/10/21 10:43:59 Error response from daemon: Cannot start container e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running container: /prosody AS /sat_pubsub/prosody Abandon I ried your suggestions : 21 octobre 2014 09:08 "Goffi" a écrit: > 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. > > Cheers > > On 21/10/2014 08:36, Goffi wrote: > >> G'day, >> >> thanks for your feedback. >> >> That's weird, why docker can't launch the container ? Can you try to >> launch it by hand ? You need to launch prosody before, so you need to >> enter: >> docker run -ti --rm --name prosody salutatoi/prosody >> docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub >> >> Before doing that, you can stop all SàT containers with >> ./libervia_cont.sh stop >> >> what do you have with "docker version" ? >> >> Do you have free space on your hard drives ? It happened several time to >> me because docker was installed on my system partition which is small... >> >> Thank you >> >> On 20/10/2014 23:52, Laura Bécognée wrote: >>> On 20/10/2014 17:51, Goffi wrote: >>>> G'day, >>>> >>>> we have just published Docker images to install easily Salut à Toi and >>>> Libervia. You can download the libervia manager script and make it >>>> executable like this: >>>> >>>> $ wget >>>> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >>>> && chmod a+x libervia_cont.sh >>>> >>>> Then to download/launch Libervia and all its dependencies, just do >>>> (once Docker is installed): >>>> $ ./libervia_cont.sh >>>> >>>> There are facilities to run, stop, update, backup, etc. >>>> >>>> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >>>> >>>> All feedbacks welcome (including the containers and the documentation). >>> >>> Hello, >>> >>> I have try to follow the process, but outch, it end up like that when I >>> launch the script : >>> >>>> d614a92cc13c: Download complete >>>> >>>> Download of latest salutatoi/data finished >>>> >>>> Running data container... OK >>>> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >>>> >>>> Running Libervia >>>> >>>> Launching prosody... OK >>>> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >>>> Launching sat_pubsub... Error, please check container or ask help on >>>> XMPP MUC sat at chat.jabberfr.org >>>> error message: >>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >>>> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >>>> Cannot link to a non running container: /prosody AS /sat_pubsub/prosody >>>> Abandon >>> >>> I'm in ubuntu 14 >>> >>> _______________________________________________ >>> dev mailing list >>> dev at goffi.org >>> http://lists.goffi.org/listinfo/dev >> >> _______________________________________________ >> dev mailing list >> dev at goffi.org >> http://lists.goffi.org/listinfo/dev > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From monsieurpaullebouanger at arghh.org Tue Oct 21 10:49:04 2014 From: monsieurpaullebouanger at arghh.org (MonsieurPaulLeBoulanger) Date: Tue, 21 Oct 2014 08:49:04 +0000 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: References: <544605E4.4060504@goffi.org> <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> <5445FF0A.10003@goffi.org> Message-ID: <32a0a998bb82267fb804f12fb624f1ec@arghh.org> Sorry :) I'm experiencing the same issue, I still have this error after the update : Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) Launching sat_pubsub... Error, please check container or ask help on XMPP MUC sat at chat.jabberfr.org error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 2014/10/21 10:43:59 Error response from daemon: Cannot start container e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running container: /prosody AS /sat_pubsub/prosody Abandon I tried your suggestions : docker run -ti --rm --name prosody salutatoi/prosody 2014/10/21 10:44:09 Error response from daemon: Conflict, The name prosody is already assigned to 273a828c9c8a. You have to delete (or rename) that container to be able to assign prosody to a container again. docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub 2014/10/21 10:44:23 Error response from daemon: Cannot start container a46f97a9a4ececa73c929f10a66d5a22cbeb7e0be18b7ab362b4037d14d9d6b4: Cannot link to a non running container: /prosody AS /jolly_pasteur/prosody docker version Client version: 1.0.1 Client API version: 1.12 Go version (client): go1.2.1 Git commit (client): 990021a Server version: 1.0.1 Server API version: 1.12 Go version (server): go1.2.1 Git commit (server): 990021a I'm also running on ubuntu 14.04.1 (32bits) 21 octobre 2014 10:46 "MonsieurPaulLeBoulanger" a écrit: > Hi, > > I'm experiencing the same issue, I still have this error after the update : > > Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) > Launching sat_pubsub... Error, please check container or ask help on XMPP MUC sat at chat.jabberfr.org > error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 > 2014/10/21 10:43:59 Error response from daemon: Cannot start container > e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running > container: /prosody AS /sat_pubsub/prosody > Abandon > > I ried your suggestions : > > 21 octobre 2014 09:08 "Goffi" a écrit: > >> 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. >> >> Cheers >> >> On 21/10/2014 08:36, Goffi wrote: >> >>> G'day, >>> >>> thanks for your feedback. >>> >>> That's weird, why docker can't launch the container ? Can you try to >>> launch it by hand ? You need to launch prosody before, so you need to >>> enter: >>> docker run -ti --rm --name prosody salutatoi/prosody >>> docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub >>> >>> Before doing that, you can stop all SàT containers with >>> ./libervia_cont.sh stop >>> >>> what do you have with "docker version" ? >>> >>> Do you have free space on your hard drives ? It happened several time to >>> me because docker was installed on my system partition which is small... >>> >>> Thank you >>> >>> On 20/10/2014 23:52, Laura Bécognée wrote: >>>> On 20/10/2014 17:51, Goffi wrote: >>>>> G'day, >>>>> >>>>> we have just published Docker images to install easily Salut à Toi and >>>>> Libervia. You can download the libervia manager script and make it >>>>> executable like this: >>>>> >>>>> $ wget >>>>> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >>>>> && chmod a+x libervia_cont.sh >>>>> >>>>> Then to download/launch Libervia and all its dependencies, just do >>>>> (once Docker is installed): >>>>> $ ./libervia_cont.sh >>>>> >>>>> There are facilities to run, stop, update, backup, etc. >>>>> >>>>> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >>>>> >>>>> All feedbacks welcome (including the containers and the documentation). >>>> >>>> Hello, >>>> >>>> I have try to follow the process, but outch, it end up like that when I >>>> launch the script : >>>> >>>>> d614a92cc13c: Download complete >>>>> >>>>> Download of latest salutatoi/data finished >>>>> >>>>> Running data container... OK >>>>> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >>>>> >>>>> Running Libervia >>>>> >>>>> Launching prosody... OK >>>>> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >>>>> Launching sat_pubsub... Error, please check container or ask help on >>>>> XMPP MUC sat at chat.jabberfr.org >>>>> error message: >>>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >>>>> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >>>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >>>>> Cannot link to a non running container: /prosody AS /sat_pubsub/prosody >>>>> Abandon >>>> >>>> I'm in ubuntu 14 >>>> >>>> _______________________________________________ >>>> dev mailing list >>>> dev at goffi.org >>>> http://lists.goffi.org/listinfo/dev >>> >>> _______________________________________________ >>> dev mailing list >>> dev at goffi.org >>> http://lists.goffi.org/listinfo/dev >> >> _______________________________________________ >> dev mailing list >> dev at goffi.org >> http://lists.goffi.org/listinfo/dev From goffi at goffi.org Tue Oct 21 11:48:07 2014 From: goffi at goffi.org (Goffi) Date: Tue, 21 Oct 2014 11:48:07 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <32a0a998bb82267fb804f12fb624f1ec@arghh.org> References: <544605E4.4060504@goffi.org> <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> <5445FF0A.10003@goffi.org> <32a0a998bb82267fb804f12fb624f1ec@arghh.org> Message-ID: <54462BD7.4050001@goffi.org> That's weird, it works OK for me, and Docker is supposed to work the same way everywhere. Do you have the same issue after "./libervia_cont.sh update" ? I'll try to install ubuntu to test it. On 21/10/2014 10:49, MonsieurPaulLeBoulanger wrote: > Sorry :) > > I'm experiencing the same issue, I still have this error after the update : > > Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) > Launching sat_pubsub... Error, please check container or ask help on XMPP MUC sat at chat.jabberfr.org > error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 > 2014/10/21 10:43:59 Error response from daemon: Cannot start container > e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running > container: /prosody AS /sat_pubsub/prosody > Abandon > > I tried your suggestions : > > docker run -ti --rm --name prosody salutatoi/prosody > 2014/10/21 10:44:09 Error response from daemon: Conflict, The name prosody is already assigned to 273a828c9c8a. You have to delete (or rename) that container to be able to assign prosody to a container again. > > docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub > 2014/10/21 10:44:23 Error response from daemon: Cannot start container a46f97a9a4ececa73c929f10a66d5a22cbeb7e0be18b7ab362b4037d14d9d6b4: Cannot link to a non running container: /prosody AS /jolly_pasteur/prosody > > > > > docker version > Client version: 1.0.1 > Client API version: 1.12 > Go version (client): go1.2.1 > Git commit (client): 990021a > Server version: 1.0.1 > Server API version: 1.12 > Go version (server): go1.2.1 > Git commit (server): 990021a > > > I'm also running on ubuntu 14.04.1 (32bits) > > > > > 21 octobre 2014 10:46 "MonsieurPaulLeBoulanger" a écrit: >> Hi, >> >> I'm experiencing the same issue, I still have this error after the update : >> >> Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) >> Launching sat_pubsub... Error, please check container or ask help on XMPP MUC sat at chat.jabberfr.org >> error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 >> 2014/10/21 10:43:59 Error response from daemon: Cannot start container >> e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running >> container: /prosody AS /sat_pubsub/prosody >> Abandon >> >> I ried your suggestions : >> >> 21 octobre 2014 09:08 "Goffi" a écrit: >> >>> 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. >>> >>> Cheers >>> >>> On 21/10/2014 08:36, Goffi wrote: >>> >>>> G'day, >>>> >>>> thanks for your feedback. >>>> >>>> That's weird, why docker can't launch the container ? Can you try to >>>> launch it by hand ? You need to launch prosody before, so you need to >>>> enter: >>>> docker run -ti --rm --name prosody salutatoi/prosody >>>> docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub >>>> >>>> Before doing that, you can stop all SàT containers with >>>> ./libervia_cont.sh stop >>>> >>>> what do you have with "docker version" ? >>>> >>>> Do you have free space on your hard drives ? It happened several time to >>>> me because docker was installed on my system partition which is small... >>>> >>>> Thank you >>>> >>>> On 20/10/2014 23:52, Laura Bécognée wrote: >>>>> On 20/10/2014 17:51, Goffi wrote: >>>>>> G'day, >>>>>> >>>>>> we have just published Docker images to install easily Salut à Toi and >>>>>> Libervia. You can download the libervia manager script and make it >>>>>> executable like this: >>>>>> >>>>>> $ wget >>>>>> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >>>>>> && chmod a+x libervia_cont.sh >>>>>> >>>>>> Then to download/launch Libervia and all its dependencies, just do >>>>>> (once Docker is installed): >>>>>> $ ./libervia_cont.sh >>>>>> >>>>>> There are facilities to run, stop, update, backup, etc. >>>>>> >>>>>> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >>>>>> >>>>>> All feedbacks welcome (including the containers and the documentation). >>>>> >>>>> Hello, >>>>> >>>>> I have try to follow the process, but outch, it end up like that when I >>>>> launch the script : >>>>> >>>>>> d614a92cc13c: Download complete >>>>>> >>>>>> Download of latest salutatoi/data finished >>>>>> >>>>>> Running data container... OK >>>>>> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >>>>>> >>>>>> Running Libervia >>>>>> >>>>>> Launching prosody... OK >>>>>> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >>>>>> Launching sat_pubsub... Error, please check container or ask help on >>>>>> XMPP MUC sat at chat.jabberfr.org >>>>>> error message: >>>>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >>>>>> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >>>>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >>>>>> Cannot link to a non running container: /prosody AS /sat_pubsub/prosody >>>>>> Abandon >>>>> >>>>> I'm in ubuntu 14 >>>>> >>>>> _______________________________________________ >>>>> dev mailing list >>>>> dev at goffi.org >>>>> http://lists.goffi.org/listinfo/dev >>>> >>>> _______________________________________________ >>>> dev mailing list >>>> dev at goffi.org >>>> http://lists.goffi.org/listinfo/dev >>> >>> _______________________________________________ >>> dev mailing list >>> dev at goffi.org >>> http://lists.goffi.org/listinfo/dev > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > From monsieurpaullebouanger at arghh.org Tue Oct 21 12:02:40 2014 From: monsieurpaullebouanger at arghh.org (MonsieurPaulLeBoulanger) Date: Tue, 21 Oct 2014 10:02:40 +0000 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: <54462BD7.4050001@goffi.org> References: <54462BD7.4050001@goffi.org> <544605E4.4060504@goffi.org> <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> <5445FF0A.10003@goffi.org> <32a0a998bb82267fb804f12fb624f1ec@arghh.org> Message-ID: same thing just after the update : Launching prosody... OK (eeb74ce27875ab9a9032916fe44f29530a3e956b6dd7cc23ca3e20aec8b8300b) Launching sat_pubsub... OK (306ff1bfa78eb078d84a1d999c0c6295e5356b4d0b8146c7602b1849b548ca82) Launching salut... Error, please check container or ask help on XMPP MUC sat at chat.jabberfr.org error message: 1469dc07f98b281074224469158bd713d4b6b59e39dbf251beabf7d1cd56c066 2014/10/21 12:01:51 Error response from daemon: Cannot start container 1469dc07f98b281074224469158bd713d4b6b59e39dbf251beabf7d1cd56c066: Cannot link to a non running container: /prosody AS /salut/prosody Abandon 21 octobre 2014 11:49 "Goffi" a écrit: > That's weird, it works OK for me, and Docker is supposed to work the > same way everywhere. Do you have the same issue after > "./libervia_cont.sh update" ? > > I'll try to install ubuntu to test it. > > On 21/10/2014 10:49, MonsieurPaulLeBoulanger wrote: > >> Sorry :) >> >> I'm experiencing the same issue, I still have this error after the update : >> >> Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) >> Launching sat_pubsub... Error, please check container or ask help on XMPP MUC > sat at chat.jabberfr.org >> error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 >> 2014/10/21 10:43:59 Error response from daemon: Cannot start container >> e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running >> container: /prosody AS /sat_pubsub/prosody >> Abandon >> >> I tried your suggestions : >> >> docker run -ti --rm --name prosody salutatoi/prosody >> 2014/10/21 10:44:09 Error response from daemon: Conflict, The name prosody is already assigned to >> 273a828c9c8a. You have to delete (or rename) that container to be able to assign prosody to a >> container again. >> >> docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub >> 2014/10/21 10:44:23 Error response from daemon: Cannot start container >> a46f97a9a4ececa73c929f10a66d5a22cbeb7e0be18b7ab362b4037d14d9d6b4: Cannot link to a non running >> container: /prosody AS /jolly_pasteur/prosody >> >> docker version >> Client version: 1.0.1 >> Client API version: 1.12 >> Go version (client): go1.2.1 >> Git commit (client): 990021a >> Server version: 1.0.1 >> Server API version: 1.12 >> Go version (server): go1.2.1 >> Git commit (server): 990021a >> >> I'm also running on ubuntu 14.04.1 (32bits) >> >> 21 octobre 2014 10:46 "MonsieurPaulLeBoulanger" a écrit: >>> Hi, >>> >>> I'm experiencing the same issue, I still have this error after the update : >>> >>> Launching prosody... OK (273a828c9c8abeb4afddc5e2f16ecb78b4ba1358197f8ad30f4b9b1f44cac61b) >>> Launching sat_pubsub... Error, please check container or ask help on XMPP MUC >> sat at chat.jabberfr.org >>> error message: e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19 >>> 2014/10/21 10:43:59 Error response from daemon: Cannot start container >>> e0cc5b30ef3a9f3ebc5613d0148c3009beb771291d38b5871c5bfff59813ea19: Cannot link to a non running >>> container: /prosody AS /sat_pubsub/prosody >>> Abandon >>> >>> I ried your suggestions : >>> >>> 21 octobre 2014 09:08 "Goffi" a écrit: >>> >>>> 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. >>>> >>>> Cheers >>>> >>>> On 21/10/2014 08:36, Goffi wrote: >>>> >>>>> G'day, >>>>> >>>>> thanks for your feedback. >>>>> >>>>> That's weird, why docker can't launch the container ? Can you try to >>>>> launch it by hand ? You need to launch prosody before, so you need to >>>>> enter: >>>>> docker run -ti --rm --name prosody salutatoi/prosody >>>>> docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub >>>>> >>>>> Before doing that, you can stop all SàT containers with >>>>> ./libervia_cont.sh stop >>>>> >>>>> what do you have with "docker version" ? >>>>> >>>>> Do you have free space on your hard drives ? It happened several time to >>>>> me because docker was installed on my system partition which is small... >>>>> >>>>> Thank you >>>>> >>>>> On 20/10/2014 23:52, Laura Bécognée wrote: >>>>>> On 20/10/2014 17:51, Goffi wrote: >>>>>>> G'day, >>>>>>> >>>>>>> we have just published Docker images to install easily Salut à Toi and >>>>>>> Libervia. You can download the libervia manager script and make it >>>>>>> executable like this: >>>>>>> >>>>>>> $ wget >>>>>>> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >>>>>>> && chmod a+x libervia_cont.sh >>>>>>> >>>>>>> Then to download/launch Libervia and all its dependencies, just do >>>>>>> (once Docker is installed): >>>>>>> $ ./libervia_cont.sh >>>>>>> >>>>>>> There are facilities to run, stop, update, backup, etc. >>>>>>> >>>>>>> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >>>>>>> >>>>>>> All feedbacks welcome (including the containers and the documentation). >>>>>> >>>>>> Hello, >>>>>> >>>>>> I have try to follow the process, but outch, it end up like that when I >>>>>> launch the script : >>>>>> >>>>>>> d614a92cc13c: Download complete >>>>>>> >>>>>>> Download of latest salutatoi/data finished >>>>>>> >>>>>>> Running data container... OK >>>>>>> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >>>>>>> >>>>>>> Running Libervia >>>>>>> >>>>>>> Launching prosody... OK >>>>>>> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >>>>>>> Launching sat_pubsub... Error, please check container or ask help on >>>>>>> XMPP MUC sat at chat.jabberfr.org >>>>>>> error message: >>>>>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >>>>>>> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >>>>>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >>>>>>> Cannot link to a non running container: /prosody AS /sat_pubsub/prosody >>>>>>> Abandon >>>>>> >>>>>> I'm in ubuntu 14 >>>>>> >>>>>> _______________________________________________ >>>>>> dev mailing list >>>>>> dev at goffi.org >>>>>> http://lists.goffi.org/listinfo/dev >>>>> >>>>> _______________________________________________ >>>>> dev mailing list >>>>> dev at goffi.org >>>>> http://lists.goffi.org/listinfo/dev >>>> >>>> _______________________________________________ >>>> dev mailing list >>>> dev at goffi.org >>>> http://lists.goffi.org/listinfo/dev >> >> _______________________________________________ >> dev mailing list >> dev at goffi.org >> http://lists.goffi.org/listinfo/dev > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev From goffi at goffi.org Wed Oct 22 14:08:24 2014 From: goffi at goffi.org (Goffi) Date: Wed, 22 Oct 2014 14:08:24 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: References: <54462BD7.4050001@goffi.org> <32a0a998bb82267fb804f12fb624f1ec@arghh.org> Message-ID: <1583456.FEHh0Wmsgr@necton3> I just realised what the issue is: images on Docker Hub don't work on 32 bits architectures (only 64 bits GNU/Linux), so you have 3 options: - install a 64 bit virtual machine - update to a 64 bit distribution - rebuild the images yourself, you need a 32 bits images of debian:jessie (I don't know if it's available somewhere, maybe you need to do it yourself), then you can do: $ hg clone http://repos.goffi.org/sat_docs $ cd docker $ ./do_all.sh build The most simple option is probably the virtual machine. I have tried a 64 bits Ubuntu 14.04 (Ubuntu server), and it works as expected there. Laura: are you on a 32 bits architecture too ? Cheers Goffi Le mardi 21 octobre 2014, 10:02:40 MonsieurPaulLeBoulanger a écrit : > same thing just after the update : > > Launching prosody... OK > (eeb74ce27875ab9a9032916fe44f29530a3e956b6dd7cc23ca3e20aec8b8300b) > Launching sat_pubsub... OK > (306ff1bfa78eb078d84a1d999c0c6295e5356b4d0b8146c7602b1849b548ca82) > Launching salut... Error, please check container or ask help on XMPP MUC > sat at chat.jabberfr.org error message: > 1469dc07f98b281074224469158bd713d4b6b59e39dbf251beabf7d1cd56c066 2014/10/21 > 12:01:51 Error response from daemon: Cannot start container > 1469dc07f98b281074224469158bd713d4b6b59e39dbf251beabf7d1cd56c066: Cannot > link to a non running container: /prosody AS /salut/prosody Abandon From llo at ygllo.com Wed Oct 22 14:55:39 2014 From: llo at ygllo.com (=?UTF-8?B?TGF1cmEgQsOpY29nbsOpZQ==?=) Date: Wed, 22 Oct 2014 14:55:39 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: <544605E4.4060504@goffi.org> References: <54452F7C.7040905@goffi.org> <54458407.2080001@ygllo.com> <5445FF0A.10003@goffi.org> <544605E4.4060504@goffi.org> Message-ID: <5447A94B.7050605@ygllo.com> 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 127.0.1.1:53: no answer from server Error while updating salutatoi/sat_pubsub > > Cheers > > On 21/10/2014 08:36, Goffi wrote: >> G'day, >> >> thanks for your feedback. >> >> That's weird, why docker can't launch the container ? Can you try to >> launch it by hand ? You need to launch prosody before, so you need to >> enter: >> docker run -ti --rm --name prosody salutatoi/prosody >> docker run -ti --rm --link prosody:prosody salutatoi/sat_pubsub >> >> Before doing that, you can stop all SàT containers with >> ./libervia_cont.sh stop >> >> what do you have with "docker version" ? >> >> Do you have free space on your hard drives ? It happened several time to >> me because docker was installed on my system partition which is small... >> >> Thank you >> >> On 20/10/2014 23:52, Laura Bécognée wrote: >>> On 20/10/2014 17:51, Goffi wrote: >>>> G'day, >>>> >>>> we have just published Docker images to install easily Salut à Toi and >>>> Libervia. You can download the libervia manager script and make it >>>> executable like this: >>>> >>>> $ wget >>>> http://repos.goffi.org/sat_docs/raw-file/tip/docker/libervia_cont.sh >>>> && chmod a+x libervia_cont.sh >>>> >>>> Then to download/launch Libervia and all its dependencies, just do >>>> (once Docker is installed): >>>> $ ./libervia_cont.sh >>>> >>>> There are facilities to run, stop, update, backup, etc. >>>> >>>> For more infomrations, check http://wiki.goffi.org/wiki/Docker/en >>>> >>>> All feedbacks welcome (including the containers and the >>>> documentation). >>> >>> Hello, >>> >>> I have try to follow the process, but outch, it end up like that when I >>> launch the script : >>> >>>> d614a92cc13c: Download complete >>>> >>>> Download of latest salutatoi/data finished >>>> >>>> Running data container... OK >>>> (bd014d0ecc23e9962a6519588175b32b00b79e98483e925bf13cdfe544586299) >>>> >>>> Running Libervia >>>> >>>> Launching prosody... OK >>>> (7f4c25a139872c8a89c67123eb7b29cc63f95ab26c1283cc700a974d301ae75f) >>>> Launching sat_pubsub... Error, please check container or ask help on >>>> XMPP MUC sat at chat.jabberfr.org >>>> error message: >>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d >>>> 2014/10/20 23:47:20 Error response from daemon: Cannot start container >>>> 8c2946a8430e1def218fecb5c5703b56409aa59b212946c77081562ffda0148d: >>>> Cannot link to a non running container: /prosody AS >>>> /sat_pubsub/prosody >>>> Abandon >>> >>> I'm in ubuntu 14 >>> >>> _______________________________________________ >>> dev mailing list >>> dev at goffi.org >>> http://lists.goffi.org/listinfo/dev >> >> >> _______________________________________________ >> dev mailing list >> dev at goffi.org >> http://lists.goffi.org/listinfo/dev > > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > -- "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." From goffi at goffi.org Wed Oct 22 16:10:41 2014 From: goffi at goffi.org (Goffi) Date: Wed, 22 Oct 2014 16:10:41 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: <5447A94B.7050605@ygllo.com> References: <54452F7C.7040905@goffi.org> <544605E4.4060504@goffi.org> <5447A94B.7050605@ygllo.com> Message-ID: <2036533.e75DoNfS0t@necton3> G'day, Le mercredi 22 octobre 2014, 14:55:39 Laura Bécognée 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 127.0.1.1:53: 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 127.0.1.1, 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 From llo at ygllo.com Thu Oct 23 22:31:01 2014 From: llo at ygllo.com (=?windows-1252?Q?Laura_B=E9cogn=E9e?=) Date: Thu, 23 Oct 2014 22:31:01 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <2036533.e75DoNfS0t@necton3> References: <54452F7C.7040905@goffi.org> <544605E4.4060504@goffi.org> <5447A94B.7050605@ygllo.com> <2036533.e75DoNfS0t@necton3> Message-ID: <54496585.50208@ygllo.com> On 22/10/2014 16:10, Goffi wrote: > G'day, > > Le mercredi 22 octobre 2014, 14:55:39 Laura Bécognée 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 127.0.1.1:53: 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 127.0.1.1, 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 Hello, 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." From goffi at goffi.org Thu Oct 23 23:10:25 2014 From: goffi at goffi.org (Goffi) Date: Thu, 23 Oct 2014 23:10:25 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <54496585.50208@ygllo.com> References: <54452F7C.7040905@goffi.org> <544605E4.4060504@goffi.org> <5447A94B.7050605@ygllo.com> <2036533.e75DoNfS0t@necton3> <54496585.50208@ygllo.com> Message-ID: <54496EC1.4060005@goffi.org> G'day Laura, > I have retry to update today, successfully \o/ (I don't respond very > early, sorry, my connection is low :-/) No worries, we are not stressed or in a hurry here ;) > > 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 > [...] That's mean that you are in 32 bits (but your computer can do 64 bits, just you have a 32 bits version of Ubuntu), and that's why the docker is not working. Docker choosed to distribute only 64 bits images on the hub. > 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 >> [...] > How can I exit this issue ? You can do "./libervia_cont.sh stop", this issue is due to the fact that you already have tried to launch the container. But as you are in 32 bits, it would not work anyway, you must use a virtual machine with e.g. Ubuntu 64 bits, or reinstall a 64 bits version... The last option is to rebuild the images, but it's not easy because you need a 32 bits version of debian:jessie. Sorry, there is not easy way :-/ Cheers Goffi From mcy at lm7.fr Thu Oct 23 23:29:45 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Thu, 23 Oct 2014 17:29:45 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: <54496EC1.4060005@goffi.org> References: <54452F7C.7040905@goffi.org> <544605E4.4060504@goffi.org> <5447A94B.7050605@ygllo.com> <2036533.e75DoNfS0t@necton3> <54496585.50208@ygllo.com> <54496EC1.4060005@goffi.org> Message-ID: <20141023172945.07debeec2a34ee7566b8b65c@lm7.fr> On Thu, 23 Oct 2014 23:10:25 +0200, Goffi wrote: > But as you are in 32 bits, it would not work anyway, you must use a > virtual machine with e.g. Ubuntu 64 bits, or reinstall a 64 bits > version... The last option is to rebuild the images, but it's not easy > because you need a 32 bits version of debian:jessie. > > Sorry, there is not easy way :-/ I wonder if installing a 64-bit kernel and the 64-bit version of docker would work. If you feel adventurous, you can try: dpkg --add-architecture amd64 aptitude update aptitude install linux-image-amd64 docker.io_ docker.io:amd64 (docker.io_ is to remove the 32-bit version of docker) Reboot on the amd64 kernel, and try again with docker. Not sure wether or not that would work. Cheers, Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From llo at ygllo.com Fri Oct 24 09:50:37 2014 From: llo at ygllo.com (=?windows-1252?Q?Laura_B=E9cogn=E9e?=) Date: Fri, 24 Oct 2014 09:50:37 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_S=E0T_and_?= =?windows-1252?q?Libervia_installable_via_Docker?= In-Reply-To: <20141023172945.07debeec2a34ee7566b8b65c@lm7.fr> References: <54452F7C.7040905@goffi.org> <544605E4.4060504@goffi.org> <5447A94B.7050605@ygllo.com> <2036533.e75DoNfS0t@necton3> <54496585.50208@ygllo.com> <54496EC1.4060005@goffi.org> <20141023172945.07debeec2a34ee7566b8b65c@lm7.fr> Message-ID: <544A04CD.80304@ygllo.com> On 23/10/2014 23:29, Matteo Cypriani wrote: > On Thu, 23 Oct 2014 23:10:25 +0200, Goffi wrote: >> But as you are in 32 bits, it would not work anyway, you must use a >> virtual machine with e.g. Ubuntu 64 bits, or reinstall a 64 bits >> version... The last option is to rebuild the images, but it's not easy >> because you need a 32 bits version of debian:jessie. >> >> Sorry, there is not easy way :-/ > I wonder if installing a 64-bit kernel and the 64-bit version of docker > would work. If you feel adventurous, you can try: > > dpkg --add-architecture amd64 > aptitude update > aptitude install linux-image-amd64 docker.io_ docker.io:amd64 > > (docker.io_ is to remove the 32-bit version of docker) > > Reboot on the amd64 kernel, and try again with docker. Not sure wether or > not that would work. > > Cheers, > Matteo Thanks Goffi and Matteo. Yep, I can't install a 64 bit version of Linux for the moment, but one day, I will, and then I will retry to install docker and make you a rapport if it work (or don't work ;) ). Glad to chat with you :) -- "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." From mcy at lm7.fr Fri Oct 24 16:06:41 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Fri, 24 Oct 2014 10:06:41 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?b?W2VuXSBTw6BUIGFuZCBMaWJl?= =?utf-8?q?rvia_installable_via_Docker?= In-Reply-To: <544A04CD.80304@ygllo.com> References: <54452F7C.7040905@goffi.org> <544605E4.4060504@goffi.org> <5447A94B.7050605@ygllo.com> <2036533.e75DoNfS0t@necton3> <54496585.50208@ygllo.com> <54496EC1.4060005@goffi.org> <20141023172945.07debeec2a34ee7566b8b65c@lm7.fr> <544A04CD.80304@ygllo.com> Message-ID: <20141024100641.549ced322bcded713cff8b69@lm7.fr> On Fri, 24 Oct 2014 09:50:37 +0200, Laura Bécognée wrote: > On 23/10/2014 23:29, Matteo Cypriani wrote: > > On Thu, 23 Oct 2014 23:10:25 +0200, Goffi wrote: > >> But as you are in 32 bits, it would not work anyway, you must use a > >> virtual machine with e.g. Ubuntu 64 bits, or reinstall a 64 bits > >> version... The last option is to rebuild the images, but it's not easy > >> because you need a 32 bits version of debian:jessie. > >> > >> Sorry, there is not easy way :-/ > > I wonder if installing a 64-bit kernel and the 64-bit version of docker > > would work. If you feel adventurous, you can try: > > > > dpkg --add-architecture amd64 > > aptitude update > > aptitude install linux-image-amd64 docker.io_ docker.io:amd64 > > > > (docker.io_ is to remove the 32-bit version of docker) > > > > Reboot on the amd64 kernel, and try again with docker. Not sure wether > > or not that would work. > > > > Cheers, > > Matteo > > Thanks Goffi and Matteo. Yep, I can't install a 64 bit version of Linux > for the moment, but one day, I will, and then I will retry to install > docker and make you a rapport if it work (or don't work ;) ). I'm not sure I made myself clear in the message above, but what I was suggesting is from your 32-bit Ubuntu, without reinstalling the whole system: it should be possible to run 64-bit processes just by running a 64-bit kernel below your current 32-bit userland. > Glad to chat with you :) Welcome here. You can also come on the chatroom (xmpp:sat at chat.jabberfr.org) if you need support or just to chat. -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: