I haven't seen that error ever before. If you Google it, people seem to have it 
in a variety of circumstances when the wrong python or virtualenv is being 
used. Have you tried a completely fresh start like I did? One of the nice 
things about docker is it's easy to start over and have a whole new set of 
containers

-- 
Dave Brondsema

> On Mar 28, 2019, at 4:53 PM, Abhishek Chaudhary 
> <abhishek.15je001...@ece.iitism.ac.in> wrote:
> 
> When I try "docker-compose run web pip install -r requirements.txt
> " I get the error message :
> Starting allura_solr_1  ... done
> Starting allura_mongo_1 ... done
> Traceback (most recent call last):
>  File "/allura-data/virtualenv/bin/pip", line 6, in <module>
>    from pip._internal import main
>  File 
> "/allura-data/virtualenv/local/lib/python2.7/site-packages/pip/_internal/__init__.py",
>  line 5, in <module>
>    import logging
>  File "/usr/lib/python2.7/logging/__init__.py", line 26, in <module>
>    import sys, os, time, cStringIO, traceback, warnings, weakref, collections
>  File "/usr/lib/python2.7/weakref.py", line 14, in <module>
>    from _weakref import (
> ImportError: cannot import name _remove_dead_weakref
> 
> & When i try to run test suite I get :
> Starting allura_mongo_1 ... done
> Starting allura_solr_1  ... done
> Traceback (most recent call last):
>  File "./run_tests", line 20, in <module>
>    import argparse
>  File "/usr/lib/python2.7/argparse.py", line 86, in <module>
>    import copy as _copy
>  File "/usr/lib/python2.7/copy.py", line 52, in <module>
>    import weakref
>  File "/usr/lib/python2.7/weakref.py", line 14, in <module>
>    from _weakref import (
> ImportError: cannot import name _remove_dead_weakref
> 
> 
> I don't actually why this is occuring because when i used to run the commands 
> before docker-compose build for a fresh start everything was working fine.
> 
>> On 2019/03/28 20:28:24, Dave Brondsema <d...@brondsema.net> wrote: 
>>> On 3/28/19 8:50 AM, Abhishek Chaudhary wrote:
>>> Hello Allura community, This is about when Ubuntu is upgraded to 18.04, 
>>> there is error in the Allura codebase while doing in Docker.
>>> When i try to start a fresh build in docker, using "docker-compose build" 
>>> command it runs but not fully supported for rest of the procedures. After 
>>> that when i try "docker-compose run web scripts/init-docker-dev.sh" . It 
>>> gives an error and for the rest of the commands too.
>>> 
>>> There is some files which are not properly imported while upgrading to 
>>> newer version of Ubuntu.
>>> Can someone look after it ?
>>> 
>>> 
>> 
>> What is the error message?
>> 
>> 
>> Works for me, ensuring a fresh start like this:
>> 
>> $ docker-compose stop
>> Stopping allura_taskd_1_7f30ee199533   ... done
>> Stopping allura_http_1_4ef8f786b48d    ... done
>> Stopping allura_inmail_1_ea0fe221d94f  ... done
>> Stopping allura_outmail_1_42845e65949b ... done
>> Stopping allura_solr_1_73afb6e91d38    ... done
>> Stopping allura_mongo_1_d1c1b46336e0   ... done
>> 
>> $ docker-compose rm
>> Going to remove allura_taskd_1_7f30ee199533, allura_http_1_4ef8f786b48d,
>> allura_inmail_1_ea0fe221d94f, allura_outmail_1_42845e65949b,
>> allura_solr_1_73afb6e91d38, allura_mongo_1_d1c1b46336e0
>> Are you sure? [yN] y
>> Removing allura_taskd_1_7f30ee199533   ... done
>> Removing allura_http_1_4ef8f786b48d    ... done
>> Removing allura_inmail_1_ea0fe221d94f  ... done
>> Removing allura_outmail_1_42845e65949b ... done
>> Removing allura_solr_1_73afb6e91d38    ... done
>> Removing allura_mongo_1_d1c1b46336e0   ... done
>> 
>> $ docker images
>> REPOSITORY          TAG                 IMAGE ID            CREATED          
>>    SIZE
>> allura_http         latest              44b2bb560f7b        9 days ago
>> 282MB
>> allura_web          latest              e8d312d2b7b9        9 days ago
>> 614MB
>> mongo               3.4                 8958526fd8a9        13 days ago
>> 390MB
>> ubuntu              18.04               94e814e2efa8        2 weeks ago
>> 88.9MB
>> solr                6-alpine            c5093230b322        2 weeks ago
>> 276MB
>> 
>> $ docker rmi 44b2bb560f7b e8d312d2b7b9 8958526fd8a9 94e814e2efa8 c5093230b322
>> ...
>> 
>> $ docker-compose build
>> ...
>> ... and the rest of the installation steps
>> 
>> 
>> 
>> -- 
>> Dave Brondsema : d...@brondsema.net
>> http://www.brondsema.net : personal
>> http://www.splike.com : programming
>>              <><
>> 
> 

Reply via email to