Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@nx-tools/nx-container
Advanced tools
Readme
@nx-tools/nx-container
The Nx Plugin for Containers contains executors, generators, and utilities for build and push containers images from your applications. It provides:
@nx-tools/nx-docker
api.This executor not handle registry login steps, so if you wanna push your container images to a remote registry, please setup the credentials using the docker login
or podman login
. For kaniko engine, you need to create the /kaniko/.docker/config.json
according to this documentation.
This is the succesor of
@nx-tools/nx-docker
. For docs about nx-docker please go check this
Adding the Container plugin to an existing Nx workspace can be done with the following:
npm install -D @nx-tools/nx-container
yarn add -D @nx-tools/nx-container
If you want an "automatic" tag management and OCI Image Format Specification for labels, you need to install the optional @nx-tools/container-metadata
package:
npm install -D @nx-tools/container-metadata
yarn add -D @nx-tools/container-metadata
@nx-tools/container-metadata is the succesor of
@nx-tools/docker-metadata
.
It's straightforward to setup your application:
nx g @nx-tools/nx-container:init appName
By default, the application will be configured with:
We can then build our application with the following command:
nx container appName
To use a different engine, you need to update the options.engine
property of your project target or use the INPUT_ENGINE environment variable. All possible values are docker
(the default), podman
and kaniko
Tip: You can set docker or podman engine in your project.json targets to use in your dev machine, and use INPUT_ENGINE env variable to use kaniko in your CI/CD pipelines.
Just change @nx-tools/nx-docker:build
to @nx-tools/nx-container:build
in your project targets and you will continue building images using the docker/buildx engine.
"docker": {
"executor": "@nx-tools/nx-container:build",
"options": {
...
}
}
Advanced usage:
Customizing
Usage with CI
Here is a list of all the executors and generators available from this package:
FAQs
The Nx Plugin for Containers contains executors, generators, and utilities for build and push containers images from your applications. It provides:
The npm package @nx-tools/nx-container receives a total of 44,025 weekly downloads. As such, @nx-tools/nx-container popularity was classified as popular.
We found that @nx-tools/nx-container demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.