Closed zeddicus76 closed 7 years ago
The 4.1 kernel networking performance in VirtualBox is pretty terrible. I would suggest sticking with the RedHat kernel (or going to 4.2).
Also, the kernel.sh
script would be the place to put any kernel code, not update.sh
, as it also manages any necessary reboots and GRUB management. If you were to provide the option to use the UEKR4 kernel, it should be managed there, as initializing the yum repo without switching to the kernel won't work, as all of the VM guest tools perform a build to match the kernel version when they install.
@annawake can you point me towards some more reading about networking performance using our UEK4 on VirtualBox? If this is indeed an issue, I'd want to get our internal teams to look into it immediately.
Note that Oracle only supports Docker on Oracle Linux using UEK4 and we only support it using the Oracle provided docker-engine (in the ol7_addons yum repository). It would be great if this process installed the Oracle-provided Docker binaries instead of the unsupported upstream binaries (or provided the choice of which to install to the build user).
This was an issue with VirtualBox 4.x - haven't tested it recently, and now we are experimenting with virtio which seems to address issues some people are seeing with network hangs/dropouts.
Closing for now. For the time being we are deferring to Docker for Mac and their desktop virtualization platform/image and Docker on Linux. These docker images were introduced before Docker for Mac existed. While the vendor solution still has numerous shortcomings and workarounds needed for networking Docker containers on the Mac, it's still overall a better experience that we are able to provide in the old bespoke docker images.
I wanted to have docker installed in the image when created so I got it working for me.