build-and-push-image

To build and push Docker container images to a Nebius registry, you need a workflow that automates registry authentication, applies correct tagging, and validates the image against your project manifest. This skill manages that end-to-end process using Docker buildx.

Container image deployment compliance for Nebius Physical AI workbenches requires enforcing packaging contracts during the build process, such as configuring non-root user permissions and setting up health checks to ensure images meet internal security baselines before deployment.

Yes, you need Docker buildx to build and validate workbench container images using this workflow. It is a required dependency for executing the builds and ensuring the resulting images adhere to the required packaging contracts.

To synchronize Dockerfile tags with image manifests for GPU cluster deployment, you must automate the resolution of registry settings and enforce manifest consistency. This skill validates that your image tags match the project packaging contract before pushing.

Limitations of automating container lifecycle management for Nebius infrastructure include strict adherence to internal security baselines for service and job images, and the requirement to use Docker buildx, which may not support custom build pipelines outside these specified packaging contracts.