simrdwn
simrdwn copied to clipboard
the error about build environment?
when the dockerfile exectue the line 99( conda install -n simrdwn2 -c defaults tensorflow-gpu=1.13.1), it always have a error ,sloving the environment failed ,when i delete the line 88 (conda update conda). the error disappeared.
when the dockerfile exectue the line 99( conda install -n simrdwn2 -c defaults tensorflow-gpu=1.13.1), it always have a error ,sloving the environment failed ,when i delete the line 88 (conda update conda). the error disappeared.
really?Have you succeed in building?
no,i have not , it also has some problems,When I execute the line 139(opencv=4.0.0)
https://hub.docker.com/r/dzynegca/simrdwn I am pulling this. Maybe you can have a try too.
thank you very much!
Hey @younkun, can you share the error? We have experienced some error in the Dockerfile and solved them on #52 and #53.
@jacquesmats Hello ,I have the same problems , the line 139 opencv=4.0.0 ,There is a conflict between opencv and gdal
I see. Did you follow the instructions on #53 ? It should work. Don't use conda forge and install just opencv not specifiying the version.
From: younkun [email protected] Sent: Thursday, July 18, 2019 10:52:41 PM To: avanetten/simrdwn Cc: Matheus Jacques; Mention Subject: Re: [avanetten/simrdwn] the error about build environment? (#58)
@jacquesmatshttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjacquesmats&data=02%7C01%7C%7C3ae2f33526e54cd1281f08d70bebc9b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636990979638972360&sdata=6PWRJjlgm7tgpaZzGyWif2bShFmm4fHK%2B2qc5I8iuh8%3D&reserved=0 Hello ,I have the same problems , the line 139 opencv=4.0.0 ,There is a conflict between opencv and gdal
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Favanetten%2Fsimrdwn%2Fissues%2F58%3Femail_source%3Dnotifications%26email_token%3DAEZ37NYPQ23XZWHQXGAELW3QAEM6TA5CNFSM4IEWFO7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KKM5I%23issuecomment-513058421&data=02%7C01%7C%7C3ae2f33526e54cd1281f08d70bebc9b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636990979638982369&sdata=ei8hdkU9OE%2FcMf%2BIrtLn%2F0dl4V5cWz0NiNBub3rxvwE%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEZ37N3HBJ2GMQBQUJI5MILQAEM6TANCNFSM4IEWFO7A&data=02%7C01%7C%7C3ae2f33526e54cd1281f08d70bebc9b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636990979638992377&sdata=q8UJv2NWYccPiSrdyfAY1U01JSsllEZDoH32K5PX3eQ%3D&reserved=0.
The most recent dockerfile builds fine as of 19 July 2019. Give that a shot. The temporary fix in #53 may build successfully, but leads to errors when running inference.