After building a docker image, I am trying to test its functionality using ContainerStructureTest#0 from azure-devops.
I have a pipeline and test configFile.
Firstly, it gives the following warning:
##[warning]Can\'t find loc string for key: FoundDockerConfigStoredInTempPath
##[warning]Can\'t find loc string for key: OldDockerConfigContent
##[warning]Can\'t find loc string for key: AddingNewAuthToExistingConfig
Then, yields the following error:
[command]/home/vsts/work/_tasks/ContainerStructureTest_39bc2c9b-55b7-4835-89cd-6cc699ef7220/0.1.2/container-structure-test test --image ***/entry_point:latest --config /home/vsts/work/1/structure-test.yaml --json
##[error]Error in executing the command: Error: spawnSync /home/vsts/work/_tasks/ContainerStructureTest_39bc2c9b-55b7-4835-89cd-6cc699ef7220/0.1.2/container-structure-test ETXTBSY
##[error]Error: Error in executing the command: Error: spawnSync /home/vsts/work/_tasks/ContainerStructureTest_39bc2c9b-55b7-4835-89cd-6cc699ef7220/0.1.2/container-structure-test ETXTBSY
I do confirm that my configFile is copied into the virtual machine:
/home/vsts/work/1/structure-test.yaml
Since your documentation is not complete yet, I followed the syntax from https://github.com/GoogleContainerTools/container-structure-test
I have a feeling that this task is not configured properly. Can anyone help me solve the error?
Related
I am trying to follow the quickstart for running the script but it is failing with this error in druid router cli:
~ $ bin/post-index-task --file quickstart/tutorial/wikipedia-index.json
bin/post-index-task: /opt/druid/bin/post-index-task-main: /usr/bin/env: bad interpreter: No such file or directory
bin/post-index-task: line 31: /opt/druid/bin/post-index-task-main: No error information
bin/post-index-task is already present but it seem to throw an error of No such file or directory.
Please guide, thanks.
I have been getting this error "The syntax of the command is incorrect". What is wrong with it?
python run.py --type evaluate --cfg_file configs/aninerf_313.yaml exp_name aninerf_313 resume True
I get the error "CRD is present in bundle but not defined in CSV" when I run make bundle.
The full output is
/Users/foobar/Documents/my-operator/bin/controller-gen "crd:trivialVersions=true,preserveUnknownFields=false" rbac:roleName=manager-role webhook paths="./..." output:crd:artifacts:config=config/crd/bases
operator-sdk generate kustomize manifests -q
cd config/manager && /Users/foobar/Documents/my-operator/bin/kustomize edit set image controller=registry.io/my-operator:latest
/Users/foobar/Documents/my-operator/bin/kustomize build config/manifests | operator-sdk generate bundle -q --overwrite --version 0.0.5
Error: accumulating resources: 2 errors occurred:
* accumulateFile error: "accumulating resources from '../samples': '/Users/foobar/Documents/my-operator/config/samples' must resolve to a file"
* accumulateDirector error: "recursed accumulation of path '/Users/foobar/Documents/my-operator/config/samples': accumulating resources: 2 errors occurred:\n\t* accumulateFile error: \"accumulating resources from 'myapplicationui.yaml': evalsymlink failure on '/Users/foobar/Documents/my-operator/config/samples/myapplicationui.yaml' : lstat /Users/foobar/Documents/my-operator/config/samples/myapplicationui.yaml: no such file or directory\"\n\t* loader.New error: \"error loading myapplicationui.yaml with git: url lacks orgRepo: myapplicationui.yaml, dir: evalsymlink failure on '/Users/foobar/Documents/my-operator/config/samples/myapplicationui.yaml' : lstat /Users/foobar/Documents/my-operator/config/samples/myapplicationui.yaml: no such file or directory, get: invalid source string: myapplicationui.yaml\"\n\n"
INFO[0000] Building annotations.yaml
INFO[0000] Writing annotations.yaml in /Users/foobar/Documents/my-operator/bundle/metadata
INFO[0000] Building Dockerfile
INFO[0000] Writing bundle.Dockerfile in /Users/foobar/Documents/my-operator
operator-sdk bundle validate ./bundle
INFO[0000] Found annotations file bundle-dir=bundle container-tool=docker
INFO[0000] Could not find optional dependencies file bundle-dir=bundle container-tool=docker
ERRO[0000] Error: Value myapplication.example.com/v1alpha1, Kind=MyApplication: CRD "myapplication.example.com/v1alpha1, Kind=MyApplication" is present in bundle "my-operator.v0.0.5" but not defined in CSV
ERRO[0000] Error: Value myapplication.example.com/v1alpha1, Kind=MyApplicationUI: CRD "myapplication.example.com/v1alpha1, Kind=MyApplicationUI" is present in bundle "my-operator.v0.0.5" but not defined in CSV
What is the cause of this error?
The error on the bottom is a red herring. The actual error is further up and uncolored when you experience it in person.
Specifically, a Kustomize yaml is expecting an myapplicationui.yaml but can't find it.
This can easily happen when someone in your team attempts to rename files (e.g. to myapplicationui_sample.yaml) without checking all of the references.
this is my test
i run the job with autodevops runner
i run this without .gitlab-ci.yaml file. but i receive the error like this.
$ if [[ -z "$CI_COMMIT_TAG" ]]; then # collapsed multi-line command
$ /build/build.sh
Building Heroku-based application using gliderlabs/herokuish docker image...
Attempting to pull a previously built image for use with --cache-from...
invalid reference format
invalid reference format
No previously cached image found. The docker build will proceed without using a cached image
invalid argument "/master:fa1708343b13496937aa567a1aecdc184f43d197" for "-t, --tag" flag: invalid reference format
See 'docker build --help'.
Cleaning up file based variables
30:00
ERROR: Job failed: command terminated with exit code 1
In appveyor I use the statement:
- initexmf --admin --force --mklinks
but due to a problem it gives the message:
initexmf --admin --force --mklinks
Sorry, but "MiKTeX Configuration Utility" did not succeed for the following reason:
Script configuration file not found.
The log file hopefully contains the information to get MiKTeX going again:
C:\ProgramData\MiKTeX\2.9\miktex\log\initexmf_admin.log
The system cannot find the path specified.
Command exited with code 1
due to the error code the process terminates and I cannot type the C:\ProgramData\MiKTeX\2.9\miktex\log\initexmf_admin.log anymore, so a bit hard to debug ...
questions:
How to continue after an error
How to stop after the outputting the file (exit 1 ?)
To run a script on failure use on_failure section, for example to push initexmf_admin.log to artifacts:
on_failure:
- appveyor PushArtifact C:\ProgramData\MiKTeX\2.9\miktex\log\initexmf_admin.log