Hi Jia: So I will first check out from cmusvsc/jpl-summerschool2016. My Docker ID is: leipan. Please add me.
Thanks, -Lei On 5/27/16, 8:31 PM, "Jia Zhang" <[email protected]> wrote: >Hi Lei: > >Starting from now, please push your new docker image to: > >cmusvsc/jpl-summerschool2016 > >Please let me know your docker id, so we can add you as collaborator at >docker hub. Thanks. > >Best regards, >Jia > >On Fri, May 27, 2016 at 8:08 PM, Qihao Bao <[email protected]> wrote: > >> Hi Lei, >> >> I saw you pushed newest version to Docker Hub. The size is 9GB on Docker >> Hub. >> I suppose that's the container for all code in master branch of our >> Github, am i right? >> >> I pulled your container from flytosky/server and pushed it to >> cmusvsc/jpl-summerschool2016. >> >> I will put our stable version of 9033 into the container for summer >>school >> this year and then we can start testing. >> >> Thanks. >> >> Wish you all a happy memorial holiday! >> >> Best, >> Qihao >> >> On Thu, May 26, 2016 at 6:12 PM, Pan, Lei (398K) <[email protected]> >> wrote: >> >>> I thought so, and the error message should have been different. >>> >>> Thanks, >>> -Lei >>> >>> > On May 26, 2016, at 4:49 PM, Qihao Bao <[email protected]> wrote: >>> > >>> > Lei, >>> > Did you run $ docker login ? >>> > You need to have authentication in order to update someone's >>>repository. >>> > >>> > Actually i have been searching for solutions for the docker-push >>> problem. >>> > But i found no official solutions nor any specific and effective >>> solutions >>> > for such issue. >>> > Someone said docker hub may be able to take containers larger than >>>10GB >>> in >>> > theory. However, when the size is very big, the push process may not >>>be >>> > successful due to unknown issues. >>> > >>> > Right now, before any solution is found, what we can do is trying to >>> shrink >>> > the size a little bit and see if it works. >>> > Thanks. >>> > >>> > Qihao >>> > >>> > On Thu, May 26, 2016 at 2:59 PM, Pan, Lei (398K) >>><[email protected]> >>> > wrote: >>> > >>> >> Probably not. So that is why I failed? How do we >>> >> deal with this? If necessary, we might be able to >>> >> remove some things inside the container. But >>> >> our integration might increase the size again. >>> >> So it is better if we can figure out a way to >>> >> accommodate a >10GB container. >>> >> >>> >> Thanks, >>> >> -Lei >>> >> >>> >> From: Qihao Bao <[email protected]<mailto:[email protected]>> >>> >> Date: Thursday, May 26, 2016 at 2:44 PM >>> >> To: JPL <[email protected]<mailto:[email protected]>> >>> >> Cc: Jia Zhang >>><[email protected]<mailto:[email protected]>>, >>> >> Seungwon Lee <[email protected]<mailto: >>> [email protected]>>, >>> >> Benyang Tang <[email protected]<mailto: >>> [email protected]>>, >>> >> "Zhai, Chengxing (398K)" <[email protected]<mailto: >>> >> [email protected]>>, >>>"[email protected]<mailto: >>> >> [email protected]>" >>><[email protected]<mailto: >>> >> [email protected]>> >>> >> Subject: Re: JPL-CMU integration >>> >> >>> >> Hi Lei, >>> >> >>> >> Have you ever successfully pushed a container which is larger than >>> 10GB to >>> >> Docker Hub? >>> >> >>> >> Docker container has 10GB size limit. >>> >> >>> >> >>> >> Qihao >>> >> >>> >> On Thu, May 26, 2016 at 2:26 PM, Pan, Lei (398K) >>><[email protected] >>> >> <mailto:[email protected]>> wrote: >>> >> Qihao: >>> >> >>> >> You cannot pull yet. I tried to push several times >>> >> but all failed. Could you please help me in identifying >>> >> what might be the cause of this failure? >>> >> >>> >> Thanks, >>> >> -Lei >>> >> >>> >> leipan@cmda-test:~$ docker push flytosky/server:v1.1 >>> >> The push refers to a repository [docker.io/flytosky/server< >>> >> http://docker.io/flytosky/server>] (len: 1) >>> >> 2c3f9829d5b6: Pushing >>> >> [==================================================>] 10.15 GB >>> >> Received unexpected HTTP status: 500 Internal Server Error >>> >> leipan@cmda-test:~$ docker commit -m 'the container for the yearly >>> >> review; ready for CMU-JPL integration; with all code checked in and >>> pushed >>> >> to github' dfdcbde445f2 flytosky/server:v1.1 >>> >> 502e0e6435a80230dcaad038d165783beb5e4c825aa3fc6461a918edfc79723c >>> >> leipan@cmda-test:~$ docker push flytosky/server:v1.1 >>> >> The push refers to a repository [docker.io/flytosky/server< >>> >> http://docker.io/flytosky/server>] (len: 1) >>> >> 502e0e6435a8: Pushing >>> >> [==================================================>] 10.86 GB >>> >> Received unexpected HTTP status: 500 Internal Server Error >>> >> leipan@cmda-test:~$ docker push flytosky/server:v1.1 >>> >> The push refers to a repository [docker.io/flytosky/server< >>> >> http://docker.io/flytosky/server>] (len: 1) >>> >> 502e0e6435a8: Pushing >>> >> [==================================================>] 10.86 GB >>> >> Received unexpected HTTP status: 500 Internal Server Error >>> >> leipan@cmda-test:~$ >>> >> >>> >> >>> >> From: JPL <[email protected]<mailto:[email protected]>> >>> >> Date: Thursday, May 26, 2016 at 1:18 PM >>> >> To: Qihao Bao <[email protected]<mailto:[email protected]>>, Jia >>>Zhang < >>> >> [email protected]<mailto:[email protected]>> >>> >> Cc: Seungwon Lee <[email protected]<mailto: >>> >> [email protected]>>, Benyang Tang <[email protected] >>> >> <mailto:[email protected]>>, "Zhai, Chengxing (398K)" < >>> >> [email protected]<mailto:[email protected]>>, " >>> >> >>>[email protected]<mailto:[email protected]>" < >>> >> [email protected]<mailto:[email protected]>> >>> >> Subject: JPL-CMU integration >>> >> >>> >> Hi Jia and Qihao: >>> >> >>> >> I have checked in the Docker container and pushed it to the Docker >>> >> container: >>> >> docker commit -m 'the container for the yearly review; ready for >>> CMU-JPL >>> >> integration; with all code checked in and pushed to github' >>> dfdcbde445f2 >>> >> flytosky/server:v1.1 >>> >> docker push flytosky/server:v1.1 >>> >> >>> >> Please pull it and use it as the container for our integration. >>> >> In particular, we would like to: >>> >> >>> >> . deploy those CMU services that are to be co-located with >>> >> the JPL services running in Cloud; >>> >> . make all services auto-start when the Docker container is played: >>> >> . for the JPL services: >>> >> . log in as the user ³svc" >>> >> . front end: cd >>> /home/svc/new_github/JPL-WebService/JPL_CMDA/frontend; >>> >> sh start.sh >>> >> . back end: cd >>> >> /home/svc/new_github/JPL-WebService/JPL_CMDA/services/svc; sh >>>start.sh >>> >> . for the CMU services: >>> >> . ?? >>> >> . develop a restful API for the JPL backend to find out the login >>> userid >>> >> on the CMU server >>> >> . address other integration requirements >>> >> >>> >> Please let me know if you have any questions and comments. >>> >> >>> >> Thanks, >>> >> -Lei >>> >> >>> >> >>> >> >>
