-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build with aliyun problem #13
Comments
What kind of error you get? Could you please provide me with more information? I don't have such a server to debug directly.. |
Acutuall I have no idea. I tried to use aliyun's free service to build my private repository to pull the container anywhere. But the master brance always fail. I have tried to build out of mainland or not, use cache or not, but always fail. But the older version like outseide-term branch works. The flowing is build log of version 18.04, other versions' log is similar, no error information:
|
Umm. This seems to be a hard problem to fix without any error information... No more logs apart from this? The apt part is fine, next should be |
The only difference between older version and master branch should be the |
there is nothing else provided by ali's contaioner service. You can try it youself. It's totally free right now. maybe the pip's "import main" problem? i notice the default version pip of ubuntu didn't work. when i build my own version of ancypwn, i used get-pip.py to upgrade to the latest version. |
Ping, is this still a problem? I've built the images several times recently, they work like a charm. |
well, i use your build on dockerhub these days. and i am still using the traditional way, the alias way of mine, as i used before. it's good enough for me right now, so i didn't try more things. |
the master branch is always faild to build directly in aliyun but outside term branch can. I'm confused about this, why?
The text was updated successfully, but these errors were encountered: