wave icon indicating copy to clipboard operation
wave copied to clipboard

On-demand containers provisioning service

Results 85 wave issues
Sort by recently updated
recently updated
newest added

When Wave access a private container registry and no credentials are provider the following error message is returned to the docker/nextflow client. ``` Task failed to start - CannotPullContainerError: Error...

The following error is thrown when digest cannot be resolved in a container manifest (stack trace is reversed): ``` 2024-03-26 18:10:10.969 17:10:10.969 [io-executor-thread-1677] INFO i.s.w.c.RegistryProxyController - > Request [HEAD] /v2/wt/cc63168b5f9b/job/genomicutils/manifests/dev...

This issue will track the progress of various documents required for wave deployments. ```[tasklist] ### Tasks - [x] Add configuration documentation - [ ] Add installation guide ```

documentation

A key capability of Wave is the build of container by providing one or more Conda or Spack packages. When relying on this mechanism the user has no control on...

Micronant 4.5.x bring some nice new feature and improvement it should be explored the impact to update Wave backend to this version

Getting a build failure using wave-cli to build the example spack image: Details ``` java.lang.IllegalStateException: Unexpected response for 'https://wave.seqera.io/v2/wt/fbdd6fcaab96/wave/build/manifests/star-2.5.4a_bwa-0.7.15--1bbd3f1023331159': [400] {"errors":[{"code":"UNKNOWN","message":"INFO[0000] Resolved base name spack/ubuntu-jammy:v0.20.0 to builder \nINFO[0000] Retrieving image...

Wave retrieves the container credentials to be used, querying Tower credentials for `container-reg` provider and looking for a matching registry name. This is convenient for users that rely on registries...

Wave currently supports 2 main container image formats, i.e Docker OCI and Singularity SIF. At the moment, the former is built with Docker via a Dockerfile recipe, whereas the latter...

There are some node groups in the prod cluster to which wave can start pods to build its images, but currently any pod may end up running on those nodes....

``` io.kubernetes.client.openapi.ApiException: Not Found at io.kubernetes.client.openapi.ApiClient.handleResponse(ApiClient.java:971) at io.kubernetes.client.openapi.ApiClient.execute(ApiClient.java:883) at io.kubernetes.client.openapi.apis.CoreV1Api.readNamespacedPodWithHttpInfo(CoreV1Api.java:45995) at io.kubernetes.client.openapi.apis.CoreV1Api.readNamespacedPod(CoreV1Api.java:45965) at io.seqera.wave.service.k8s.K8sServiceImpl.getPod(K8sServiceImpl.groovy:189) at io.seqera.wave.service.k8s.K8sServiceImpl.waitPod(K8sServiceImpl.groovy:366) at io.seqera.wave.service.builder.KubeBuildStrategy.build(KubeBuildStrategy.groovy:66) at io.seqera.wave.service.builder.ContainerBuildServiceImpl.launch(ContainerBuildServiceImpl.groovy:125) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at...