This repository has been archived by the owner on May 12, 2021. It is now read-only.
rpc error: code = Internal desc = Could not set name eth2 for interface file exists: unknown #785
Projects
Comments
|
No not related with #702 |
|
Hi @fredbcode - thanks for reporting. However, it's difficult to see what is happening because the proxy log errors captured when you ran If you are running on a dev / test box and are happy to lose your journal log, it would be useful if you could clear the journal and re-run:
|
|
What are interfaces in all containers? Seems there is already a "eth2" interface? |
|
There is no ethX at all but enspX, yes network is ready and the same
docker-compose works well without kataruntime (on same machine of course)
I don't known where kata find this eth2
|
|
@jodh-intel I will provide logs tomorrow |
|
@fredbcode - thanks ;) |
|
Haveged installed (see #702) cat /proc/sys/kernel/random/entropy_avail Full log enabled and purged Sorry I can't use kata-log-parser on this sever. kata.txt |
docker-compose up without kata This message is useless: |
|
Without |
|
@amshinde any thoughts from the network side on the eth1/eth2 info here? |
|
Maybe related to different nic naming "ethXX" vs "enoXX". |
|
I guess I found something very interesting ! But with only two internal networks: I'm exactly in the same situation that before with issue #702 with Kata only one or two containers works well (but here my entropy is 4066) My Dockerfile contains only a FROM to registry - ubuntu image - |
|
Of course I mean, max two containers works well -> containers with network in this case |
|
Syslog: |
|
/cc @sboeuf, @amshinde, @mcastelino. |
|
@amshinde @mcastelino correct me if I'm wrong but I think |
|
Good question @sboeuf - and that is not going to surprise me. I think we have not tested Kata with docker compose much/enough. If this is the answer, can we check we have this in our Limitations do, and if not, add it. |
|
+1. But also I wonder if there is a way for us to detect this scenario and fail elegantly? |
|
Tried without ipv6 (I have a lot of warnings about) without success, someone can try to reproduce with this simple docker-compose ?
Comment and uncomment a network and sometimes image works, sometimes not
A kill command is needed I'm pretty sure that there is also a timeout/exhausted resources issue here, because right after the same docker-compose can works (if kata-proxy is well dead) A complete sequence: |
|
Here some tests I made, I'm trying to reproduce what docker-compose does: A bash script with: works well ! docker inspect testu1 And FI same issue with: Let me know if I can help you in any way |
|
Latest dockerd build : docker version 18.06.1-ce, build e68fc7a I have this message in syslog only when the bug occurs: Oct 4 08:59:38 TEST-001 dockerd[28865]: time="2018-10-04T08:59:38.993840460Z" level=error msg="1337c9b768f7bfaff38e10ae54156ddedd1e064e8a71e69eeda9b91bac9beb2d cleanup: failed to delete container from containerd: no such container" Docker in debug mode Same without error (with only two networks) It works, although I have this in debug message (but nothing in prompt after docker-compose up)
|
|
Hello there. Is there any workaround to use kata-runtime with docker-compose ? |
|
Hello, |
|
Ping @amshinde @mcastelino - any thoughts, input or requests for more tests/info here?
|
|
Le 10/10/2018 à 10:42, Frank Cao a écrit :
We have integrated with k8s. For docker-compose, I'm afraid most of
use haven't used it.
You can easily reproduce with a basic docker-compose here:
#785 (comment)
|
|
Hello there, output result : |
|
@sboeuf @grahamwhaley We do have a current limitation with docker-compose that causes issues in dns name resolution due to the use of |
|
@fredbcode @Gabasjob This patch to the runtime should solve your issue for now: Can you give that a shot. I am planning to open a PR with that fix. |
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Oct 11, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
|
Great, can you share with us a binary please ? |
|
@fredbcode - we don't really have the facility to do that. But all you'd need to do is:
|
|
I will soon, thanks |
|
@jodh-intel |
|
Excellent! - thanks @Gabasjob , and kudos @amshinde |
|
I also confirm, great ! |
|
Great - sounds like #814 will dtrt then ;) |
|
@grahamwhaley dns issue still present I'm affraid : output without kata-runtime : output with kata-runtime : |
|
@Gabasjob yep - that is a known limitation. |
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Oct 11, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Oct 11, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Oct 11, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> (cherry picked from commit 8f1b28d)
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Oct 11, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> (cherry picked from commit 8f1b28d)
amshinde
added a commit
to amshinde/kata-runtime
that referenced
this issue
Oct 11, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> (cherry picked from commit 8f1b28d)
|
@grahamwhaley Unfortunately there are no workarounds for this due to the way name resolution is handled in docker for custom networks. |
zklei
pushed a commit
to zklei/runtime
that referenced
this issue
Nov 22, 2018
Sort endpoints by name to control the order in which they are passed to the VM as the interface name inside the VM depends on the order in which it is passed. Long term we should come up with a more robust approach. Fixes kata-containers#785 Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
egernst
pushed a commit
to egernst/runtime
that referenced
this issue
Feb 9, 2021
Makefile: do not use LDFLAGS to avoid environment contamination
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description of problem
docker-compose up stop with an error message (works without kataruntime)
Expected result
All dockers image runs
Actual result
ERROR: for app_apache-rp_1 Cannot start service apache-rp: OCI runtime create failed: rpc error: code = Internal desc = Could not set name eth2 for interface &{{3 1500 1000 eth1 02:42:ac:14:00:03 broadcast|multicast 4098 0 0 0xc4202940e0 0 0xc420017760 ether down 0 0 0 []}}: file exists: unknown
ERROR: for apache-rp Cannot start service apache-rp: OCI runtime create failed: rpc error: code = Internal desc = Could not set name eth2 for interface &{{3 1500 1000 eth1 02:42:ac:14:00:03 broadcast|multicast 4098 0 0 0xc4202940e0 0 0xc420017760 ether down 0 0 0 []}}: file exists: unknown
ERROR: Encountered errors while bringing up the project.
Meta details
Running
kata-collect-data.shversion1.3.0-rc1 (commit 22aedc4)at2018-09-25.12:56:13.961551045+0000.Runtime is
/usr/bin/kata-runtime.kata-envOutput of "
/usr/bin/kata-runtime kata-env":Runtime config files
Runtime default config files
Runtime config file contents
Config file
/etc/kata-containers/configuration.tomlnot foundOutput of "
cat "/usr/share/defaults/kata-containers/configuration.toml"":Image details
Initrd details
No initrd
Logfiles
Runtime logs
Recent runtime problems found in system journal:
Proxy logs
Recent proxy problems found in system journal:
Shim logs
Recent shim problems found in system journal:
Container manager details
Have
dockerDocker
Output of "
docker version":Output of "
docker info":Output of "
systemctl show docker":No
kubectlPackages
Have
dpkgOutput of "
dpkg -l|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"":No
rpmPerhaps related with #702
proxy.log
runtime.log
shim.log
The text was updated successfully, but these errors were encountered: