-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
How to build docker 1.13 on FreeBSD 11? #31303
Comments
|
@justincormack Do you know anyone trying to support FreeBSD? |
|
The port was never upstreamed, so it cannot be built from this repository.
There is some interest in restarting a port, maybe we should create an
issue to track this.
…On 26 Feb 2017 20:00, "Akihiro Suda" ***@***.***> wrote:
dockerd is not supported on FreeBSD.
@justincormack <https://github.com/justincormack> Do you know anyone
trying to support FreeBSD?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31303 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAdcPPUm9IX0uO7MK9mS5aDGwXiOPjT0ks5rgkp6gaJpZM4MKcZD>
.
|
|
Well this is unfortunate. Back in late 2015 there have been numerous news on tech blogs going like this: "Docker now officially supported on FreeBSD" which got my hopes up. But since I didn't use it back then I just memorized it as nice info. Now I have seen that there is just this one port from @kvasdopil that was made in 7/15 as a (as it seems) one time thing. Which makes this kind of a useless endeavour. As I have seen a "FreeBSD" build icon (even though it is disabled) and some Issue entries regarding FreeBSD, I was just thinking that it might work anyway, if I just compiled it for myself. Dang EDIT: |
|
The current build is just for a Freebsd client.
…On 27 Feb 2017 08:06, "Stefan Wendler" ***@***.***> wrote:
Well this is unfortunate. Back in late 2015 there have been numerous news
on tech blogs going like this: "Docker now officially supported on FreeBSD"
which got my hopes up. But since I didn't use it back then I just memorized
it as nice info. Now I have seen that there is just this one port from
@kvasdopil <https://github.com/kvasdopil> that was made in 7/15 as a (as
it seems) one time thing. Which makes this kind of a useless endeavour. As
I have seen a "FreeBSD" build icon (even though it is disabled) and some
Issue entries regarding FreeBSD, I was just thinking that it might work
anyway, if I just compiled it for myself. Dang
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31303 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAdcPHXV15nH5g7jwRvLoWD4og3q2Ds9ks5rgvSRgaJpZM4MKcZD>
.
|
|
Just my experiments with Freebsd 11. $go version $cd /tmp $cp /tmp/docker/vendor/github.com/docker/libnetwork/ns/init_linux.go /tmp/docker/vendor/github.com/docker/libnetwork/ns/init_freebsd.go $./hack/make.sh Does syscall.Gettid, syscall.NETLINK_ROUTE, syscall.NETLINK_XFRM, syscall.AF_NETLINK, syscall.NETLINK_XFRM not exist for Freebsd? So, I did move it all from init_freebsd.go for testing only! import ( ) $./hack/make.sh $ls -l /tmp/docker/bundles/17.04.0-dev/binary-client/docker-17.04.0-dev |
|
Test with syscall.Gettid, syscall.NETLINK_ROUTE, syscall.NETLINK_XFRM, syscall.AF_NETLINK, syscall.NETLINK_XFRM. $cat syscall.go $GOOS=freebsd GOARCH=amd64 go build syscall.go $GOOS=linux GOARCH=amd64 go build syscall.go |
|
Before porting dockerd you would need to port run c. |
|
I'll go ahead and close this issue, because compiling for FreeBSD won't work currently (without someone working on porting it), but feel free to continue the conversation |
I can't seem to find any information on this. The docker-freebsd port is unmaintained since 2015 and running make.sh on the git clone fails with:
But since some people use docker with FreeBSD I assume there is a way to run it?
I need some support here, please
Thanks so much
The text was updated successfully, but these errors were encountered: