Moby VS Vcpkg

Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.

Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...

Try to use moby instead since that is the engine in Docker.

https://github.com/moby/moby

> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.

Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780

It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)

Perhaps.

Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.

Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.

AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...

5.4.5 can be compromised

https://github.com/microsoft/vcpkg/issues/37197

vcpkg may expire assets after 1.5 years, so achieve long-term reproducibility you will need to cache your dependencies.... Somewhere. Not sure what the expected solution is.

https://github.com/microsoft/vcpkg/pull/30546#issuecomment-1...

There were various approaches recommended depending on our language and ecosystem. My classmates who developed using Node.js were recommended npm, and PyPI or poetry for Python. Since my program is written in C++, I was recommended to look into one of vcpkg or conan, but I ultimately did not use either package manager.

Which dependencies are not in vcpkg? We can ask them to add it. It’s pretty easy just open an issue there https://github.com/microsoft/vcpkg/issues .

./vcpkg search netcdf gdal[netcdf] Enable NetCDF support minc 2.4.03#3 MINC - Medical Image NetCDF or MINC isn't netCDF minc[minc1] Support minc1 file format, requires NETCDF netcdf-c 4.8.1#2 A set of self-describing, machine-independent data formats that support th... netcdf-c[dap] Build with DAP remote access client support netcdf-c[hdf5] Build with HDF5 support netcdf-c[nczarr] Build with NCZarr cloud storage access support netcdf-c[nczarr-zip] Build with NCZarr ZIP support netcdf-c[netcdf-4] Build with netCDF-4 support netcdf-c[platform-default-features] Enable platform-dependent default features netcdf-c[tools] Build utilities netcdf-cxx4 4.3.1#4 a set of machine-independent data formats that support the creation, acces... The result may be outdated. Run `git pull` to get the latest results. If your port is not listed, please open an issue at and/or consider making a pull request. - https://github.com/Microsoft/vcpkg/issues

The hyperscan update to vcpkg seems to have happened from 5.4.0 to 5.4.2 in this commit on Apr 20.

Dear Fictrac team, I am hoping to install Fictrac in our windows 11 x64 laptop (Visual Studio 2019, cMake 3.26.4). I followed the installation guideline on github page fictrac and used the latest vcpkg

This works fine if one wants to do stuff like clang main.cpp -lvulkan, or even find_package(Vulkan REQUIRED) in CMake, but it doesn't define VULKAN_SDK, and therefore doesn't work with vcpkg's Vulkan support, for instance. A fair bit of Vulkan development, tutorials, etc. assume that the entire SDK is installed, as-is.