-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Why not use Dockerfile for build #93
Comments
Can you send the output log of the build issue you got? |
I got:
I think it's because my golang is too old:
Now I'm using |
ya its because of the old golang version and faced the same issue and when i changed it to 1.4 then i dont see this issue any where.Try using gvm when your facing issues like this so that u can change ur golang versions anytime |
I think there is already a dockerfile in the repo dont know if it is useful for you https://github.com/opencontainers/runc/blob/master/test_Dockerfile |
No reason, we can add one if you want ;) |
Implementations page
I see there are several build issues, myself met build issues too, I wonder why we don't use Dockerfile to setup an unified environment for building?
I thought runc was considered as an independent project which won't depend on Docker or other projects, but then I see we still use Docker for test, so I think we can use Docker for build as well.
Is there any specific reasons why we don't use Dockerfile? Thanks.
The text was updated successfully, but these errors were encountered: