chore: Bump Node-RED container to 4.0.4 #649
nodered-container.yml
on: pull_request
Build 2.2.3 container images
/
build
1m 40s
Build 3.0.2 container images
/
build
1m 41s
Build 3.1.x container images
/
build
1m 50s
Build 4.0.x container images
/
build
39s
Upload image to production ECR
/
deploy
Upload image to staging ECR
/
deploy
Upload image to production ECR
/
deploy
Upload image to staging ECR
/
deploy
Upload image to production ECR
/
deploy
Upload image to staging ECR
/
deploy
Upload image to production ECR
/
deploy
Upload image to staging ECR
/
deploy
Annotations
1 error and 3 warnings
Build 4.0.x container images / build
buildx failed with: ERROR: failed to solve: nodered/node-red:4.0.4-20: failed to resolve source metadata for docker.io/nodered/node-red:4.0.4-20: docker.io/nodered/node-red:4.0.4-20: not found
|
Sensitive data should not be used in the ARG or ENV commands:
node-red-container/Dockerfile-2.2.x#L4
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "REGISTRY_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Sensitive data should not be used in the ARG or ENV commands:
node-red-container/Dockerfile#L4
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "REGISTRY_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Sensitive data should not be used in the ARG or ENV commands:
node-red-container/Dockerfile-3.1#L4
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "REGISTRY_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
FlowFuse~helm~1UW7J4.dockerbuild
|
63.3 KB |
|
FlowFuse~helm~B7S0AX.dockerbuild
|
62 KB |
|
FlowFuse~helm~UOQ4IK.dockerbuild
|
57.3 KB |
|
FlowFuse~helm~YAKKHP.dockerbuild
|
9.21 KB |
|