Creating containers from a local image registry

[k-gostev]

From the Eclipse Kanto Dev Mailing list:

Q: From eduleen.talledo@fpt.com:

May I ask questions about kanto-cm?
We are currently creating a POC leveraging kanto-cm features.
However, we encountered issues over issues in our setup and stuck for a week already. 😄

Background:

• In a our ubuntu vm, we have 2 containers.
  • container 1 = local docker registry
  • container 2 = container with kanto setup (eclipse leda)
• We tried pulling feedercan from ghcr.io/eclipse/kuksa.val.feeders/dbc2val:v0.1.1.
  • Then we pushed it in our local docker registry tagged localhost:5000/feedercan:latest
  • Verified feedercan exist in localhost:5000/v2/_catalog.
• When we do systemctl restart contianer-management.service in contianer 2 it cannot find it.
  • kanto-cm have errors.
  • time="2024-05-23T12:10:47.479274512Z" level=info msg="trying next host" error="failed to do request: Head "[http://localhost:5000/v2/feedercan/manifests/latest](http://localhost:5000/v2/feedercan/manifests/latest/)": dial tcp [::1]:5000: connect: connection refused" host="localhost:5000"
• We also configured config.json to allow insecure_registries.
  
• I attached a small logfile in kanto-cm.
  

My questions are:

1. Can we pull images from our local docker registry?
2. Where and how can we setup kanto-cm images.json file so that kanto-cm will read it after systemctl restart contianer-management.service?

==========================
A: from @dimitar-dimitrow:
Here are some instructions for setting up a local registry and then use it with kanto-cm:

kanto-cm create --ports 5000:5000 --e REGISTRY_STORAGE_DELETE_ENABLED=true --name registry docker.io/library/registry:latest
kanto-cm start -n registry
docker pull hello-world:latest
docker tag hello-world:latest localhost:5000/hello-world:latest
docker push localhost:5000/hello-world:latest
kanto-cm create -n hello --rp no localhost:5000/hello-world:latest
kanto-cm start --a -n hello

JSON files with container configurations are handled be the deployment sub-service within Kanto Container Management. The default directory is /etc/container-management/containers. It is configurable of course, you can check the doc and here are the default deployment values:

{
    "deployment": {
        "enable": true,
        "mode": "update",
        "home_dir": "/var/lib/container-management",
        "ctr_dir": "/etc/container-management/containers"
    }
}

=============================
Q: From eduleen.talledo@fpt.com:
I did the instructions below but still cannot pull like registry.

root@cf7c7fcl6dfe:/# kanto-cm create --ports 12345:5000 - -name registry docker.1o/library/registry:latest
FATA [2024 - 05 - 27T15: 40:14.788579804Z]
error while dialing /run/container-management/container-management.sock: context deadline exceeded

This is the container-management.log

This is my config.json.

After editing the config.json and creating dir in etc/container-management/containers.
I restarted container-management.service before running the command kanto-cm create.

I'm not sure what did I missed? 😄

Also does kanto-cm have its own registry?
If ever has, how to use it? (push, pull, etc).

[dimitar-dimitrow]

After editing the config.json and creating dir in etc/container-management/containers.
I restarted container-management.service before running the command kanto-cm create.

I'm not sure what did I missed? 😄

The error from container-management.log is irrelevant to the create command. The kanto-cm CLI and CM daemon communicate through the container-management.sock. However it could not dial to the socket, maybe the CM daemon failed to start and create the socket. Could you check whether the container-management.service is running? It may have failed to start due to invalid configuration json format(although the config from the picture looks fine). When there is a fail before the logger is configured, there would be no entries in container-management.log. For such failures , you can check the journal - journalctl -r -u container-management.service(keep in mind that the log is reversed, latest logs are at the top)>

---

Also does kanto-cm have its own registry?
If ever has, how to use it? (push, pull, etc)

Kanto Container Management is a container engine(like Docker and Podman), it is lightweight, so it could be run on the edge(limited hardware). The container engines typically do have an ability to pull/push images from/to a registry. Kanto CM only has the ability to pull images, this is done to keep the CM lightweight as possible and it is not expected to manage your container registries from an edge device. The pulling of the image is done during container creation.

You can run container image that set up a container registry on every container engine, including Kanto CM:

kanto-cm create --ports 5000:5000 --e REGISTRY_STORAGE_DELETE_ENABLED=true --name registry docker.io/library/registry:latest

[eduleent]

Hello,

I apologize for the late response.
What is actually happening in our POC is that we ran kanto-cm inside docker.
There are errors when we try to run it inside the docker container like sysfs error something.
We try to avoid installing anything in our edge device aside from docker. ^^

In the end, we installed kanto locally in our edge device since we did not encounter a single error. ^^
Then deployed containers from velocitas and kuksa flawlessly.

We already concluded the project but I have a question.
Does kanto support kanto-in-docker? like docker-in-docker?
Though it would be nice to support it (wish list). ^^

Thank you,
Eduleen