singularity-cri
singularity-cri copied to clipboard
sylabs
The Singularity implementation of the Kubernetes Container Runtime Interface
The singularity-cri and wlm-operator projects were created by Sylabs to explore interaction between the Kubernetes and HPC worlds. In 2020, rather than dilute our efforts over a large number of...
What are the steps to reproduce this issue? ------------------------------------------- 1. …create deployment (test.yaml) using local.file prefix for container 'image' (image: local.file/local/home/user1/testapp.sif) as per CRI documentation (Thirdly, aiming HPC users needs,...
What are the steps to reproduce this issue? ------------------------------------------- 1. Create a kubernetes deployment 2. Pods fail to be deployed What happens? ------------- Pods fail to be created with: ```...
What are the steps to reproduce this issue? ------------------------------------------- 1. Configure Kubernetes to use Singularity CRI What happens? ------------- Pods scheduled by `coredns` and `dns-autoscaler` deployments reflect a status of...
I've managed to solve the issue, but I'm not sure if the manual config was needed due to something on my end or if it's an issue with documentation. What...
I'm helping @kalle1024 with [this issue](https://github.com/singularityhub/sregistry/issues/209) and we were wondering how a user could go about installing custom software? Would it come down to rebuilding some base image (customized) and...
What are the steps to reproduce this issue? ------------------------------------------- 1. Clone singularity CRI 2. Checkout the v1.0.0-beta.v7 tag 3. Run make What happens? ------------- Singularity CRI fails to build What...
Some background: I am working in a corporate environment where `noexec` and `nodev` are set on `/tmp` and all internet access must be done through a proxy. Usually when working...
### my kubelet.service config is: [Unit] Description=Kubernetes Kubelet Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=docker.service Requires=docker.service [Service] WorkingDirectory=/var/lib/kubelet ExecStart=/opt/kube/bin/kubelet \ --address=10.2.152.182 \ --allow-privileged=true \ --anonymous-auth=false \ --authentication-token-webhook \ --authorization-mode=Webhook \ --client-ca-file=/etc/kubernetes/ssl/ca.pem \ --cluster-dns=10.70.0.2 \ --cluster-domain=cluster.local....
What are the steps to reproduce this issue? ------------------------------------------- 1. Install Kubernetes with kubeadm 2. Install singularity-cri from master branch 3. modify kubeadm-flags to point singularity socket sudo cat /var/lib/kubelet/kubeadm-flags.env...
