Docker Vendor Lock-In and Proprietary Dockerfile Syntax
4/10 LowDevelopers fear vendor lock-in with Docker's proprietary toolchain. While Dockerfile syntax is not governed by open standards, the OCI image and runtime specifications provide alternatives. Developers increasingly prefer solutions aligned with open standards to avoid single-vendor dependency and ensure long-term portability.
Sources
Collection History
What is proprietary, however, is the snap store, the place where applications are distributed. Snaps are another controversial point, that I would tend to put in the 'they invented another way to do things instead of contributing to an already existing model' locker.
Though generally embraced, even the Dockerfile syntax is not controlled by an open standard like the OCI image and runtime requirements. Especially when open standards promise more flexibility and long-term stability, developers prefer to avoid being limited to a single toolchain.