Anyone has any idea how I can correct this error? Seems templates on GitLab don't work.
ERROR: Job failed (system failure): Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"rootfs_linux.go:58: mounting \\\"/var/lib/docker/volumes/runner-mh5zgyxe-project-119-concurrent-0-cache-c33bcaa1fd2c77edfc3893b41966cea8/_data\\\" to rootfs \\\"/var/lib/docker/overlay2/19e6d863d0d048b030aa4702ee47667085a8e571c266b9623294c4ac68e7c8da/merged\\\" at \\\"/var/lib/docker/overlay2/19e6d863d0d048b030aa4702ee47667085a8e571c266b9623294c4ac68e7c8da/merged/builds\\\" caused \\\"mkdir /var/lib/docker/overlay2/19e6d863d0d048b030aa4702ee47667085a8e571c266b9623294c4ac68e7c8da/merged/builds: no space left on device\\\"\"": unknown (docker.go:817:0s)
Related
While running the dataflow template in python using the following command
gcloud dataflow flex-template run "streaming-beam-`date +%Y%m%d-%H%M%S`" \
--template-file-gcs-location "$TEMPLATE_PATH" \
--region "$REGION"
The job gets triggered on the console but the DAG is not formed and the following error is reported after a couple of minutes
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/opt/google/dataflow/python_template_launcher\": stat /opt/google/dataflow/python_template_launcher: no such file or directory": unknown.
Can someone figure out what the problem could be?
I have already checked the following
The template file is present in the location
The registry has the image
Not sure what the error means?
I was trying to re-implement this code from Github and it requires me to install nvidia-docker and run it. The installation of nvidia-docker seemed successful. However, when I run the command nvidia-docker run -it --ipc=host deep-colorization, it throws the following error::
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 1 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: driver error: failed to process request\\\\n\\\"\"": unknown.
ERRO[0002] error waiting for container: context canceled
I am not sure what the error means as I don't have any previous experience with the docker ecosystem. Any kind of assistance is appreciated. I am running Ubuntu 18 by the way.
Thanking you in advance.
I received this error upon starting my network.
Command Used :
./byfn.sh up
Operating System :
Windows 10 pro
Error :
OCI runtime exec failed: exec failed: container_linux.go:348: starting
container process caused "exec: \"scripts/script.sh\": stat
scripts/script.sh: no such file or directory": unknown ERROR !!!! Test
failed
I have installed monitoring out of the box according to this link:
http://www.jhipster.tech/monitoring/
When I start with:
docker-compose up -d
Everything starts but not Elastalert:
First log:
ERROR: for monitoring_jhipster-alerter_1 Cannot start service jhipster-alerter: OCI runtime create failed: container_linux.go:296: starting container process caused "process_linux.go:398: container init caused \"rootfs_linux.go:58: mounting \\"/Users/john/source/intellij/company/app/myservice/alerts/config.yaml\\" to rootfs \\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged\\" at \\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged/opt/elastalert/config.yaml\\" caused \\"not a directory\\"\"": unknown: Are you trying to mount a direStarting monitoring_jhipster-import-dashboards_1
Second log:
ERROR: for jhipster-alerter Cannot start service jhipster-alerter: OCI runtime create failed: container_linux.go:296: starting container process caused "process_linux.go:398: container init caused \"rootfs_linux.go:58: mounting \\"/Users/john/source/intellij/company/app/myservice/alerts/config.yaml\\" to rootfs \\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged\\" at \\"/var/lib/docker/overlay2/5657c6e9e7bb2be5cf4fa9860c04269e34be15641f4e3f0c1449af7cbf82ced5/merged/opt/elastalert/config.yaml\\" caused \\"not a directory\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
Using the default docker-compose.yml file that I got with:
curl -O https://raw.githubusercontent.com/jhipster/jhipster-console/master/bootstrap/docker-compose.yml
Im not sure what this messages says?
This is because the volumes path for JHipster Alerter is incorrect. Change
jhipster-alerter:
image: jhipster/jhipster-alerter:latest
environment:
- ES_HOST=jhipster-elasticsearch
- ES_PORT=9200
volumes:
- ../jhipster-alerter/rules/:/opt/elastalert/rules/
- ../alerts/config.yaml:/opt/elastalert/config.yaml
To
- ../alerts/rules/:/opt/elastalert/rules/
- ../jhipster-alerter/config.yaml:/opt/elastalert/config.yaml
As shown in https://github.com/jhipster/jhipster-console/pull/102/commits/fa5bc75ec29ca357477ac1a22203ae6cbe2af2f7.
We are running Linux RHEL v6.4 where we have Jube 2.0.33 installed. Jube is running with below env vars set
export https_proxy=
export http_proxy=
export DOCKER_REGISTRY=
export KUBERNETES_MASTER=
export FABRIC8_CONSOLE=
Now, we are using below command after setting above env vars to build simple project (contained at quickstarts-master\quickstarts\java\simple-mainclass - from Github samples)
mvn clean install jube:build fabric8:json fabric8:deploy
The build becomes successful, however when we go to jube fabric8 hawtio console and try to run application... we don't see pods running... instead we see below stacktrace printed on jube server console.
Stack trace says the built image is trying to be uploaded to external maven repos which we don't want.... we tried setting "upload" xml element in maven to "false" too.... however still no luck, we end up seeing same stack trace.
ERROR: Failed to create pod: quickstart-camel-servlet-8. java.io.IOException: Failed to resolve mvn:io.fabric8.jube.images.fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/zip/image. org.sonatype.aether.collection.DependencyCollectionException: Failed to collect dependencies for io.fabric8.jube.images.fabric8:quickstart-war-camel-servlet:zip:image:2.2-SNAPSHOT (runtime)
java.io.IOException: Failed to resolve mvn:io.fabric8.jube.images.fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/zip/image. org.sonatype.aether.collection.DependencyCollectionException: Failed to collect dependencies for io.fabric8.jube.images.fabric8:quickstart-war-camel-servlet:zip:image:2.2-SNAPSHOT (runtime)
Caused by: org.sonatype.aether.collection.DependencyCollectionException: Failed to collect dependencies for io.fabric8.jube.images.fabric8:quickstart-war-camel-servlet:zip:image:2.2-SNAPSHOT (runtime)
Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for io.fabric8.jube.images.fabric8:quickstart-war-camel-servlet:zip:image:2.2-SNAPSHOT
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not transfer artifact io.fabric8.jube.images.fabric8:quickstart-war-camel-servlet:pom:2.2-SNAPSHOT from/to central (http://repo1.maven.org/maven2): Error transferring file: null to http://repo1.maven.org/maven2/io/fabric8/jube/images/fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/quickstart-war-camel-servlet-2.2-SNAPSHOT.pom
Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact io.fabric8.jube.images.fabric8:quickstart-war-camel-servlet:pom:2.2-SNAPSHOT from/to central (http://repo1.maven.org/maven2): Error transferring file: null to http://repo1.maven.org/maven2/io/fabric8/jube/images/fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/quickstart-war-camel-servlet-2.2-SNAPSHOT.pom
Caused by: org.apache.maven.wagon.TransferFailedException: Error transferring file: null to http://repo1.maven.org/maven2/io/fabric8/jube/images/fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/quickstart-war-camel-servlet-2.2-SNAPSHOT.pom
at org.sonatype.maven.wagon.AhcWagon.fillInputData(AhcWagon.java:301)
Caused by: java.io.IOException: null to http://repo1.maven.org/maven2/io/fabric8/jube/images/fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/quickstart-war-camel-servlet-2.2-SNAPSHOT.pom
Caused by: java.net.ConnectException: null to http://repo1.maven.org/maven2/io/fabric8/jube/images/fabric8/quickstart-war-camel-servlet/2.2-SNAPSHOT/quickstart-war-camel-servlet-2.2-SNAPSHOT.pom
at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:95)
Caused by: java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Net.java:127)
Any help to resolve this is greatly appreciated.
Thanks in advance