Sasha Yakovtseva

Yes, of course :)

@sanketmlad Still the error output looks like it is docker, not Singularity. On your node where you want to run SIF, do: 1. Install Singularity 2. Install and launch Singularity-CRI...

Hello @sanketmlad, Did you manage to make it work so far?

Hi @malixian, Please provide the following information: - OS distribution and version - `go version` - Singularity-CRI version (`sycri version`) - `singularity version` - `kubectl version` - pod specification you...

@malixian What version of singularity-cri you are using? Can you confirm the same network error appears if you do `singularity pull library://malixian/default/test-arm64:latest` on that host?

@malixian Is this is not an issue anymore? Looks like you have accidentally closed it. And I need a full output of `kubectl describe no ` and `sycri version`.

Can you please update sycri to the latest version? Also node information says you are running docker. I think you pasted the wrong node info here. According to your pod...

> your suggestion is update sycri to 1.0.0-beta.6 Yes, there've been some fixes

Also enabling debug logs will help us to understand what is wrong. In sycri service add `-v 6` option to sycri command and then restart services (assuming systemd is used):...

Is that for `sashayakovtseva/test/image-server`? That image was built for `amd64`, so if you are scheduling it to `arm` it fails to start.