Answers: <p>As you can't build a docker image for an arm kernel from a x86 one neither.</p>
  
  <p>Nor can't you build an image with a glibc lib targetting a 4.x kernel on a host running a 3.X kernel.</p>
  
  <p>Docker isolate processes and give a virtual filesystem but that's still the host kernel who own the process, so obviously without a layer of hardware virtualization like virtualbox, vmware, xen, kvm, there's no chance to build an image with binaries made for a different kernel type.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-09-28T12:07:59.667Z
Answers: 2017-09-28T12:07:59.667Z
Answers: Tensibai
Body: <p>I know that in generally it is impossible to build FreeBSD Docker image on Linux host OS due to different kernels and sys calls. <a href="https://forums.docker.com/t/trouble-when-i-want-to-used-freebsd-images/3309/2" rel="nofollow noreferrer">Relevant discussion</a>.</p>
  
  <p>However, I would like to know maybe there is a simple workaround to overcome this limitation?</p>
  
  <p>P.S. I don't want to consider Vagrant usage inside Docker container and I don't want to consider usage of FreeBSD as host OS.</p>
  
Tags: <docker><linux>
Title: Build FreeBSD Docker image using Ubuntu host OS
UserDisplayName: user54
ThreadText: # Build FreeBSD Docker image using Ubuntu host OS
  
  (Asked by: username_0 on 2017-09-28)
  
  I know that in generally it is impossible to build FreeBSD Docker image on Linux host OS due to different kernels and sys calls. [Relevant discussion](https://forums.docker.com/t/trouble-when-i-want-to-used-freebsd-images/3309/2).
  
  However, I would like to know maybe there is a simple workaround to overcome this limitation?
  
  P.S. I don't want to consider Vagrant usage inside Docker container and I don't want to consider usage of FreeBSD as host OS.
  
  **Tags:** docker, linux
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-09-28. Score: 5 | Accepted answer
  
  As you can't build a docker image for an arm kernel from a x86 one neither.
  
  Nor can't you build an image with a glibc lib targetting a 4.x kernel on a host running a 3.X kernel.
  
  Docker isolate processes and give a virtual filesystem but that's still the host kernel who own the process, so obviously without a layer of hardware virtualization like virtualbox, vmware, xen, kvm, there's no chance to build an image with binaries made for a different kernel type.
  
  
  ---
  
  