levantando docker

soyasi · August 4, 2022, 4:47am

He instalado docker y antes de correr el contenedor que quería, he hecho un systemctl status docker y me ha arrojado lo siguiente

ago 04 02:00:38 tuf systemd[1]: Starting Docker Application Container Engine…
ago 04 02:00:38 tuf dockerd[6873]: time=“2022-08-04T02:00:38+01:00” level=info msg=“SUSE:secrets :: enabled”
ago 04 02:00:38 tuf dockerd[6891]: time=“2022-08-04T02:00:38+01:00” level=warning msg="containerd config version 1 has been deprecated and will be removed in containerd v2.0, please switch to version 2, see https://github.com/containerd/containerd/blob/main/docs/PL>
ago 04 02:00:38 tuf dockerd[6891]: time=“2022-08-04T02:00:38.534334402+01:00” level=warning msg=“failed to load plugin io.containerd.snapshotter.v1.devmapper” error=“devmapper not configured”
ago 04 02:00:38 tuf dockerd[6891]: time=“2022-08-04T02:00:38.534729983+01:00” level=warning msg=“could not use snapshotter devmapper in metadata plugin” error=“devmapper not configured”
ago 04 02:00:38 tuf dockerd[6891]: time=“2022-08-04T02:00:38.535342351+01:00” level=error msg=“failed to initialize a tracing processor “otlp”” error=“no OpenTelemetry endpoint: skip plugin”
ago 04 02:00:38 tuf dockerd[6873]: time=“2022-08-04T02:00:38.590502979+01:00” level=warning msg=“Your kernel does not support CPU realtime scheduler”
ago 04 02:00:38 tuf dockerd[6873]: time=“2022-08-04T02:00:38.590702167+01:00” level=warning msg=“Your kernel does not support cgroup blkio weight”
ago 04 02:00:38 tuf dockerd[6873]: time=“2022-08-04T02:00:38.590754129+01:00” level=warning msg=“Your kernel does not support cgroup blkio weight_device”
ago 04 02:00:39 tuf systemd[1]: Started Docker Application Container Engine.

aunque he visto el resultado, he corrido el programa y ha funcionado a la perfección en este caso el docker de “truecommand”](https://hub.docker.com/r/ixsystems/truecommand)

Me imagino que al funcionarme el programa, no debería de preocuparme del tema, pero como no es un tema que domine, me ha entrado curiosidad.
sobre todo del mensaje de error, que no encuentro mucho en san google.

¿alguna idea del error?

saludos

DiabloRojo · August 4, 2022, 7:24am

Parece un problema del plugin otlp con respecto al docker.
Aquí hay unas posibles soluciones:
https://github.com/microsoft/WSL/issues/8450
https://stackoverflow.com/questions/72654492/opentelemetry-exporter-endpoint-is-not-working-in-docker

soyasi · August 6, 2022, 4:33pm

Encontré una solución, pero es engorrosa, lo soluciona mientras tengo el demonio activo, pero una vez que lo paro tengo que ejecutarlo de nuevo.

si hago un systemctl start docker, me sale el fallo

si clono el plugin de git clone https://github.com/open-telemetry/opentelemetry-specification

y hago make, cuando termina de compilar busca el docker y se integra, desapareciendo el fallo

systemctl status docker
**●** docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
     Active: **active (running)** since Sat 2022-08-06 15:11:02 WEST; 5min ago
       Docs: http://docs.docker.com
   Main PID: 31345 (dockerd)
      Tasks: 55
     CGroup: /system.slice/docker.service
             ├─31345 /usr/bin/dockerd --add-runtime oci=/usr/sbin/docker-runc
             └─31364 containerd --config /var/run/docker/containerd/containerd.toml --log-level warn

ago 06 15:11:42 tuf dockerd[691]: time="2022-08-06T15:11:42+01:00" level=info msg="SUSE:secrets :: enabled"
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.033153604+01:00" level=warning msg="cleaning up after shim disconnected" id=fc4a0d238e885cf91b4b5968676f916f16b342031f2ec0e3c59933579d40a7ac namespace=moby
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.039199342+01:00" level=warning msg="cleanup warnings time=\"2022-08-06T15:11:43+01:00\" level=info msg=\"starting signal loop\" namespace=moby pid=741 runtime=io.containerd.runc.v2
"
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.398808313+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.398917824+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.398954980+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.399647526+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/0e79988ed0cc3fd7a87da1ccf6aae9896063f3df83e12301ad17b09758a943c1 pi>
ago 06 15:11:43 tuf dockerd[857]: time="2022-08-06T15:11:43+01:00" level=info msg="SUSE:secrets :: enabled"
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.617854782+01:00" level=warning msg="cleaning up after shim disconnected" id=0e79988ed0cc3fd7a87da1ccf6aae9896063f3df83e12301ad17b09758a943c1 namespace=moby
ago 06 15:11:43 tuf dockerd[31364]: time="2022-08-06T15:11:43.642214293+01:00" level=warning msg="cleanup warnings time=\"2022-08-06T15:11:43+01:00\" level=info msg=\"starting signal loop\" namespace=moby pid=898 runtime=io.containerd.runc.v2
"

si hago un “systemctl restart docker” vuelve aparecer el fallo, porque obviamente, ya no se queda integrado/acoplado el plugin.

si vuelvo a ejecutar el docker y vuelvo a ejecutar el make del plugin vuelve a buscarlo y se vuelve a acoplar/integrar y desaparece el fallo.

No se como solucionarlo, para que se quede integrado definitivamente.

solo me permite make.

si intento hacer el make del plugin con el demonio de docker parado, sale la advertencia:

docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See ‘docker run --help’.
make: *** [Makefile:83: table-check] Error 125

Mis conocimientos para esto estan limitados.

DiabloRojo · August 9, 2022, 2:45pm

Si te defiendes con el ingles, reporta el fallo en el Bugzilla de openSUSE.
Un comentario, mirando en mi Leap 15.3, tengo este paquete

sudo zypper se -v opentelemetry
| python3-opentelemetry-api | paquete | 0.5b0-bp153.1.14 | noarch       | Repositorio principal

Mirando en el buscador de paquetes de openSUSE me aparece varios, míralo tu mismo: https://software.opensuse.org/search?baseproject=ALL&q=opentelemetry

No se como va el tema con tu gecko. Igual el problema es de la versión de otlp que esta desfasada.

soyasi · August 9, 2022, 6:22pm

el paquete lo tengo instalado, si miro /usr/share/doc/packages/python3-opentelemetry-api/README.rst, me daba la opción de instalarlo con pip, así que lo desinstalo y lo intento con

pip install opentelemetry-api

pip install opentelemetry-api  
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.
pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.                                                                                                                                                           
Collecting opentelemetry-api
  Using cached opentelemetry-api-0.6b0.tar.gz (22 kB)
    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-WPM2SW/opentelemetry-api/setup.py'"'"'; __file__='"'"'/tmp/pip-install-WPM2SW/opentelemetry-api/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code
=f.read().replace('"'"'
'"'"', '"'"'
'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-rJ76YX                                                                                                                      
         cwd: /tmp/pip-install-WPM2SW/opentelemetry-api/                                                                                                                                                                                                                       
    Complete output (5 lines):                                                                                                                                                                                                                                                 
    Traceback (most recent call last):                                                                                                                                                                                                                                         
      File "<string>", line 1, in <module>                                                                                                                                                                                                                                     
      File "/tmp/pip-install-WPM2SW/opentelemetry-api/setup.py", line 53, in <module>                                                                                                                                                                                          
        packages=setuptools.find_namespace_packages(                                                                                                                                                                                                                           
    AttributeError: 'module' object has no attribute 'find_namespace_packages'                                                                                                                                                                                                 
    ----------------------------------------                                                                                                                                                                                                                                   
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

El resultado es ese; eso sí, intenta instalar opentelemetry-api-0.6b0.tar.gz, que es superior a la de los repositorios.

Hace tiempo que no reporto nada en bugzilla, porque mi ingles es de parvulitos y el traductor ya me ha jugado malas pasadas anteriormente.

soyasi · August 9, 2022, 8:22pm

El problema no se ha corregido con el plugin, aunque descubrí que estaba mal mi instalación, te dejo como lo hice:

ago 09 18:56:20 tuf dockerd[11288]: time="2022-08-09T18:56:20.796453576+01:00" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"

he aprovechado para corregir el problema que tenía en python:

python -m pip uninstall pip
zypper remove python2-pip
whereis pip
pip:

wget https://bootstrap.pypa.io/pip/3.6/get-pip.py -O /tmp/get-pip.py

**python3 /tmp/get-pip.py                                              **

Collecting pip<22.0
  Using cached pip-21.3.1-py3-none-any.whl (1.7 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 21.3.1
    Uninstalling pip-21.3.1:
      Successfully uninstalled pip-21.3.1
Successfully installed pip-21.3.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

soyasi@tuf:~> pip install --user pipenv

Collecting pipenv
  Downloading pipenv-2022.4.8-py2.py3-none-any.whl (3.6 MB)
     |████████████████████████████████| 3.6 MB 1.8 MB/s             
Collecting virtualenv-clone>=0.2.5
  Downloading virtualenv_clone-0.5.7-py3-none-any.whl (6.6 kB)
Requirement already satisfied: pip>=18.0 in /usr/lib/python3.6/site-packages (from pipenv) (21.3.1)
Requirement already satisfied: setuptools>=36.2.1 in /usr/lib/python3.6/site-packages (from pipenv) (44.1.1)
Requirement already satisfied: virtualenv in /usr/lib/python3.6/site-packages (from pipenv) (16.1.0)
Requirement already satisfied: certifi in /usr/lib/python3.6/site-packages (from pipenv) (2018.1.18)
Installing collected packages: virtualenv-clone, pipenv
  WARNING: The script virtualenv-clone is installed in '/home/soyasin/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.                                                                                                                                                           
  WARNING: The scripts pipenv and pipenv-resolver are installed in '/home/soyasin/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.                                                                                                                                                           
Successfully installed pipenv-2022.4.8 virtualenv-clone-0.5.7

soyasi@tuf:~> pip3 install --user pipenv

Requirement already satisfied: pipenv in ./.local/lib/python3.6/site-packages (2022.4.8)
Requirement already satisfied: certifi in /usr/lib/python3.6/site-packages (from pipenv) (2018.1.18)
Requirement already satisfied: virtualenv-clone>=0.2.5 in ./.local/lib/python3.6/site-packages (from pipenv) (0.5.7)
Requirement already satisfied: virtualenv in /usr/lib/python3.6/site-packages (from pipenv) (16.1.0)
Requirement already satisfied: pip>=18.0 in /usr/lib/python3.6/site-packages (from pipenv) (21.3.1)
Requirement already satisfied: setuptools>=36.2.1 in /usr/lib/python3.6/site-packages (from pipenv) (44.1.1)

soyasi@tuf:~> echo “PATH=$HOME/.local/bin:$PATH” >> ~/.profile
soyasi@tuf:~> source ~/.profile
soyasi@tuf:~> whereis pip
pip: /usr/bin/pip

soyasi@tuf:~> **pip install opentelemetry-api**
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: opentelemetry-api in /usr/lib/python3.6/site-packages (0.5b0)
Collecting aiocontextvars
  Downloading aiocontextvars-0.2.2-py2.py3-none-any.whl (4.9 kB)
Requirement already satisfied: contextvars==2.4 in /usr/lib/python3.6/site-packages (from aiocontextvars->opentelemetry-api) (2.4)
Requirement already satisfied: immutables>=0.9 in /usr/lib64/python3.6/site-packages (from contextvars==2.4->aiocontextvars->opentelemetry-api) (0.18)
Requirement already satisfied: typing-extensions>=3.7.4.3 in /usr/lib/python3.6/site-packages (from immutables>=0.9->contextvars==2.4->aiocontextvars->opentelemetry-api) (4.1.1)
Installing collected packages: aiocontextvars
Successfully installed aiocontextvars-0.2.2

soyasi@tuf:~> **pip show opentelemetry-api**
Name: opentelemetry-api
Version: 0.5b0
Summary: OpenTelemetry Python API
Home-page: https://github.com/open-telemetry/opentelemetry-python/tree/master/opentelemetry-api
Author: OpenTelemetry Authors
Author-email: cncf-opentelemetry-contributors@lists.cncf.io
License: Apache-2.0
Location: /usr/lib/python3.6/site-packages
Requires: aiocontextvars
Required-by:

DiabloRojo · August 10, 2022, 3:36pm

Estabas usando Python 2 en vez de Python 3 que tienes instalado. El salto de la versión 2 a la 3 es muy grande y los programas o aplicaciones que usan la 2 puede no funcionar en la 3 y viceversa.