Issues creating containers & links with basic topology #370
Comments
qlyoung
changed the title
|
Hi @qlyoung Before going into the errors themselves, I wanted to point out some issues I see with the endpoints configuration: links:
- endpoints: ["fhr:eth0", "rp:eth0"]
- endpoints: ["lhr:eth0", "rp:eth1"]You shouldn't have
If your intention was to interconnect if, on the other hand, you wanted all the nodes to share the management network, then no Let me know what was the topology you wanted to build and we can sort it out :) |
|
Ok, I'll switch to |
|
New topology: root@buster /h/v/lab# cat lab.yaml
name: pim-basic
topology:
nodes:
rp:
kind: linux
image: frrouting/frr:v7.5.0
fhr:
kind: linux
image: frrouting/frr:v7.5.0
lhr:
kind: linux
image: frrouting/frr:v7.5.0
source:
kind: linux
image: alpine:latest
consumer:
kind: linux
image: alpine:latest
links:
- endpoints: ["fhr:eth1", "rp:eth1"]
- endpoints: ["lhr:eth1", "rp:eth2"]This summarizes the topology I want for now, just New output: Looks like So now the only issues are
For 2, I destroyed the lab, restarted Docker, and spun up the lab again. This time two containers are missing, |
|
If it helps you can spin up the same VM with https://app.vagrantup.com/debian/boxes/buster64 I installed containerlab with and docker with |
|
I'll check this lab first on my system and see if the issue appears there
But I can suggest you to try and install docker as it explained in docker
docs, it is now docker-ce package that needs to be installed
…On Thu, 8 Apr 2021 at 18:43, Quentin Young ***@***.***> wrote:
If it helps you can spin up the same VM with
vagrant init debian/buster64
vagrant up
https://app.vagrantup.com/debian/boxes/buster64
I installed containerlab with
bash -c "$(curl -sL https://get-clab.srlinux.dev)"
and docker with
apt install docker.io
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#370 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5P3UI2VFBV3ELF34B3THXMLRANCNFSM42SG2ACQ>
.
|
|
The |
|
As you see from the docker version output, docker.io dates back to 2018. We
haven't tested such an old version of docker, as such our docs state that
we require docker ce 19 at a minimum
While the issue that you see might not be related to outdated docker
version, it is still recommended to run a maintained/fresh version of
docker which is a docker-ce nowadays
…On Thu, 8 Apr 2021 at 19:13, Quentin Young ***@***.***> wrote:
The docker-ce package is the one provided by docker themselves; docker.io
is the one provided by distributions. I would expect clab to work with
distro docker packages. I'll try using docker-ce and report back.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#370 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5KA6WH6UJ5V37Y34YLTHXP4NANCNFSM42SG2ACQ>
.
|
|
I tried with By default this VM image has 512 mb of memory. I went back to the initial environment, increased memory to 4gb, and the errors disappeared. However, I feel the error output should have included something about OOM. If that's not feasible it might be prudent to make a note of what OOM failures look like, since it's not really clear (not seeing the usual Shall I close this or leave it open for tracking that? |
|
Ah, yes, resources...
Let's close this and I will open the new one to warn about memory
requirements
…On Thu, 8 Apr 2021 at 19:27, Quentin Young ***@***.***> wrote:
I tried with docker-ce on a new VM, and it failed in a different way. One
that showed me what the real problem is:
***@***.***:/home/vagrant/lab# free -m
total used free shared buff/cache available
Mem: 483 145 185 2 152 322
Swap: 0 0 0
By default this VM image has 512 mb of memory.
I went back to the initial environment, increased memory to 4gb, and the
errors disappeared.
However, I feel the error output should have included something about OOM.
Shall I close this or leave it open for tracking that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#370 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5MXFCRAOPFQOVJOBMTTHXRRXANCNFSM42SG2ACQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This project is extremely cool. Thank you for building it.
I took it for a spin and hit a few issues I'd appreciate some help with.
Environment: Debian 10 (buster)
Kernel:
Linux buster 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/LinuxArch: x64
Docker version:
containerlab version:
This is a stock Debian 10 VM running under Virtualbox.
Description
I wrote the following topology file:
I then run
containerlab deploy --topo lab.yaml.Here's the output:
The issues I noticed:
rphas two interfaces defined in the topology, but I only see one veth created in the running container:sourceis reported ascreatedin the initialdeployoutput, and ininspectoutput, and does not appear indocker psand is in fact not running. I've seen this happen withfhron another attempt so it seems to be random which container doesn't make it:Am I doing something wrong? Let me know if you need any additional info.
The text was updated successfully, but these errors were encountered: