Unable to create a new image for a v16.0 project

[hbto]

When trying to create a new image for projects

git@git.vauxoo.com:vauxoo/somostotem.git in v16.0

and

git@git.vauxoo.com:vauxoo/gandalf.git in v16.0

Two different projects not yet related to one another

They fail with following message:

fatal: unable to access 'https://github.com/Vauxoo/emacs.d.git/': getaddrinfo() thread failed to start

Having tried several times. It always fails at the same spot.

In the case of gandalf it does not fail when performing the procedure for v15.0

It seems it is a odoo-version-related issue.

t2d is updated

pip install -U travis2docker 
Requirement already up-to-date: travis2docker in /home/hbto/.local/lib/python3.8/site-packages (6.4.8)
Requirement already satisfied, skipping upgrade: Jinja2==3.1.*; python_version >= "3.7" in /home/hbto/.local/lib/python3.8/site-packages (from travis2docker) (3.1.2)
Requirement already satisfied, skipping upgrade: PyYAML==6.0.*; python_version >= "3.7" in /home/hbto/.local/lib/python3.8/site-packages (from travis2docker) (6.0)
Requirement already satisfied, skipping upgrade: MarkupSafe>=2.0 in /home/hbto/.local/lib/python3.8/site-packages (from Jinja2==3.1.*; python_version >= "3.7"->travis2docker) (2.1.1)

I am using the switch --deployv and --build-env-args=VIM_INSTALL

[luisg123v]

@rolandojduartem this is the same error message you were getting, isn't it?

[rolandojduartem]

@luisg123v, yes, it is. Here the thing is that I could create the image for nortenas 16.0 on Pop!_OS 22.04 LTS 21 hours ago, but when I was creating the same image on Ubuntu 16.04.2 LTS 8 hours ago the process failed showing the same message.

[moylop260]

It is related to docker version + ubuntu version in the container (in this case v16.0 use Ubuntu 22.04)

You need to upgrade your docker (server) installation in order to fix the issue

If you have installed in the host use the following instructions: https://docs.docker.com/engine/install/

if you are using docker-machine (e.g. raditz or nappa...) you can upgrade using

docker-machine upgrade NAME-MACHINE

See the docker machine name using docker-machine ls

[rolandojduartem]

Hi, @moylop260, I tried to build a image for kukyflor and it failed in my computer (no Raditz), the log is here. In some point, you can read "fatal: destination path '/home/odoo/.emacs.d' already exists and is not an empty directory.". In mycomputer is installed:

• travis2docker 6.4.8
• Docker version 23.0.1, build a5ee5b1
• OS Pop!_OS 22.04 LTS

[moylop260]

Notice this issue is not related with t2d

You can reproduce the same error using only docker and the quay.io image generated before

For the Humberto example it could be:

docker run -it --rm quay.io/vauxoo/nocustomers:gandalf-16.0-cc1917b git clone --depth 1 -b master https://github.com/Vauxoo/emacs.d.git /home/odoo/.emacs.d

The output from my local is the following:

• 

If you run the same command and you have reproduced the error you need to fix your docker server environment itself

[moylop260]

BTW @allanpa88 recently reported a similar issue related but it was reproduced running: docker run --rm -it ubuntu:22.04 apt update

Something like

GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.

Notice it is using the vanilla docker image and it is running a basic command

Or try the following:

docker run -it registry.fedoraproject.org/fedora:rawhide curl google.com You could see the following error: curl: (6) getaddrinfo() thread failed to start

So, only to double-confirm it is not related to t2d or quay.io image generated

[moylop260]

I found the issue related: https://github.com/moby/moby/issues/42680#issue-953683711

Notice the docker version must be > 20.10.7

[hbto]

@moylop260 I will try your recommendations and will let you know in about two hours from now.

Regards.

[hbto]

Thanks a lot guys,

Using https://docs.docker.com/engine/install/ubuntu/#installation-methods

I was able to fix the problem.

I have upgraded my version of docker from:

to: