Open bryteise opened 6 years ago
I'm running F26 on the host then booting clr using start_qemu.sh clear-19530-kvm.img
and starting a Clear Container. The only change I needed to make was to start_qemu.sh
to increase the memory assigned to the hypervisor (from 1024
to 4096
).
Is this error repeatable for you (for new installations)?
The error is coming from virtcontainers but points to an issue with the agent running inside the guest O/S.
@sboeuf - any ideas?
If it is repeatable, please enable the proxy debug option and re-run to see if you get anything else in the journal:
Description of problem
docker fails to start container the first time it is attempted to be run
Expected result
docker run succeeds the first time
Actual result
root@clr-0552865481254b448d6c45c2a317a0c7 ~ # uname -r
4.14.1-446.native
proxyclr-0552865481254b448d6c45c2a317a0c7 ~ # systemctl enable --now docker cc3-
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /usr/lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/multi-user.target.wants/cc3-proxy.service → /usr/lib/systemd/system/cc3-proxy.service.
root@clr-0552865481254b448d6c45c2a317a0c7 ~ # docker run -it clearlinux
Unable to find image 'clearlinux:latest' locally
latest: Pulling from library/clearlinux
a59415a85b4b: Pull complete
Digest: sha256:2cf6333893ae5e28ab1645d9f448430f06167c791a9f9aee5976f81c573e3791
Status: Downloaded newer image for clearlinux:latest
docker: Error response from daemon: exit status 1: "CMD ID received 8 not matching expected 9\n".
(the next docker run -it clearlinux works)
Meta details
Running
cc-collect-data.sh
version3.0.8 (commit )
at2017-11-22.00:56:52.901084570
.Runtime is
/usr/bin/cc-runtime
.cc-env
Output of "
/usr/bin/cc-runtime cc-env
":Runtime config files
Runtime default config files
Runtime config file contents
Config file
/etc/clear-containers/configuration.toml
not found Output of "cat "/usr/share/defaults/clear-containers/configuration.toml"
":Logfiles
Runtime logs
Recent runtime problems found in system journal:
Proxy logs
No recent proxy problems found in system journal.
Shim logs
No recent shim problems found in system journal.
Container manager details
Have
docker
Docker
Output of "
docker info
":No
kubectl
Packages
No
dpkg
No
rpm