-
This is the error that I am getting right now:
Error invoking remote method 'docker-start-container': Error: (HTTP code 500) server error - failed to create shim task: OCI runtime create failed: ru…
-
```
Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused
"process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"…
-
Hi @sakaki- it's me again.
Thanks for your time in advance.
**TL;DR;** I'm having the following error `OCI runtime create failed: container_linux.go:349: starting container process caused "apply c…
-
As of now, the runtime lifecycle states that there is a `Start` action which results in creation of a container sandbox and spawning the first process inside the container.
It would be better to separ…
vishh updated
7 years ago
-
Hi,
I run below script to package smart contract:
docker exec -e CHANNEL_NAME=tradechannel -e CC_LANGUAGE=node -e CC_LABEL=trade -e CC_VERSION=v1 trade_cli cli_scripts/chaincode.sh package
T…
-
**[Problem encoutered]**
My teammate and I are implementing an container runtime which will start container by systemd. In order to make the container runtime cooperate with containerd(so that we can…
-
### Info:
- Docker version (`$ docker --version`): 18.09.0, build 4d60db4
- Nodedock commit (`$ git rev-parse HEAD`): f830d8f
- System info (Mac, PC, Linux): Mac
- System info disto/version: 10.14…
-
Propose to update the Runtime spec to allow for null or empty in the `Windows.layerFolder` field. I found an issue where this wasn't being parsed correctly: https://github.com/containers/oci-spec-rs/…
-
arm platform should have a govariant beside goarch and goos. Without that we "overwrite" armv6 and armv7 architecture containers in our registry, because goarch is always "arm".
-
One of the reasons I want to use Replicate is that I don't have an nvidia GPU.
But for some reason I'm unable to push a model without actually having an nvidia GPU, since the "validating" step tries …