platform.sh - lando rebuild - Resolving ftp.us.debian.org (ftp.us.debian.org)... failed

mttkng commented 3 years ago

Lando v3.4.3 on MacOS 11.6

After installing the update (was on 3.4.2 before that), rebuilding or destroying and starting again gives me this error;

Resolving ftp.us.debian.org (ftp.us.debian.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'ftp.us.debian.org'
ERROR ==> wget: unable to resolve host address 'ftp.us.debian.org'

If I just run wget http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb directly on the command line it works fine.

Full output from rebuild;

Killing aecf_db_1         ... done
Killing aecf_rediscache_1 ... done
Killing aecf_app_1        ... done
Going to remove aecf_db_1, aecf_rediscache_1, aecf_app_1
Removing aecf_db_1         ... done
Removing aecf_rediscache_1 ... done
Removing aecf_app_1        ... done
Pulling rediscache ... done
Pulling app        ... done
Pulling db         ... done
app uses an image, skipping
db uses an image, skipping
rediscache uses an image, skipping
landoproxyhyperion5000gandalfedition_proxy_1 is up-to-date
Creating aecf_app_1 ... done
Manually Installing DPKG...
--2021-10-07 17:02:17--  http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'ftp.us.debian.org'
ERROR ==> wget: unable to resolve host address 'ftp.us.debian.org' 
Creating aecf_db_1         ... done
Creating aecf_rediscache_1 ... done
Opening platform.sh containers... this may take a bit...
Scanning to determine which services are ready... Please standby...

  _      __              _           __
 | | /| / /__ ________  (_)__  ___ _/ /
 | |/ |/ / _ `/ __/ _ \/ / _ \/ _ `/_/ 
 |__/|__/\_,_/_/ /_//_/_/_//_/\_, (_)  
                             /___/     

Your app started up but we detected some things you may wish to investigate.
These only may be a problem.

 ■ One of your build steps failed
   This **MAY** prevent your app from working.
   Check for errors above, fix them in your Landofile, and try again by running:
   lando rebuild

Here are some vitals:

 NAME      aecf                    
 LOCATION  /Volumes/Repos/aecf     
 SERVICES  app, db, rediscache     
 APP URLS  http://localhost:50770  
           http://aecf.lndo.site/  
           https://aecf.lndo.site/

Tell us about your .lando.yml

name: aecf
recipe: platformsh
config:
  id: ###########
tooling:
  composer:
    service: app
  wp:
    service: app
  composer-install:
    description: Install Composer dependencies
    cmd: ./bin/install-composer-dependencies.sh
    service: app

xaqrox commented 3 years ago

Same here, wget http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb works both on host machine and inside lando ssh.

xaqrox commented 3 years ago

This appears to be happening on ALL my platform.sh builds...

thasmo commented 3 years ago

Having a related issue where it is able to connect to the repository but fails afterwards when installing:

Scanning to determine which services are ready... Please standby...
Manually Installing DPKG...
--2021-10-08 06:56:42--  http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... 208.80.154.15, 64.50.236.52, 64.50.233.100, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|208.80.154.15|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2115334 (2.0M) [application/octet-stream]
Saving to: 'dpkg_1.18.25_amd64.deb'
...
...
...
Manually Installing gcc-6-base, libc6, & libgcc1...
...
...
...
Setting up libc6:amd64 (2.24-11+deb9u4) ...

Configuration file '/etc/ld.so.conf.d/x86_64-linux-gnu.conf'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** x86_64-linux-gnu.conf (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/ld.so.conf.d/x86_64-linux-gnu.conf ...
/usr/bin/perl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/bin/perl)
dpkg: error processing package libc6:amd64 (--install):
 subprocess installed post-installation script returned error exit status 1
dpkg: libgcc1:amd64: dependency problems, but configuring anyway as you requested:
 libgcc1:amd64 depends on libc6 (>= 2.14); however:
  Package libc6:amd64 is not configured yet.

Setting up libgcc1:amd64 (1:6.3.0-18+deb9u1) ...
Errors were encountered while processing:
 libc6:amd64
ERROR ==> libc6:amd64

thasmo commented 3 years ago

Using 3.4.0 seems to work. Tested 3.4.1, 3.4.2, 3.4.3 which all result in the mentioned error.

daggerhart commented 3 years ago

Downgrading to 3.4.0 allowed be to start the project. But afterwards I couldn't lando pull because of the ssl cert being expired.

chris-archer-whisky commented 3 years ago

I also have the same issue. on 3.4.3

thasmo commented 3 years ago

Downgrading to 3.4.0 allowed be to start the project. But afterwards I couldn't lando pull because of the ssl cert being expired.

I solved this separately somehow; beause in the end, I was upgrading to 3.4.1+ to fix the SSL issues, which it did. But they're now gone at the moment using 3.4.0. Not sure why tho. :thinking:

philltran commented 3 years ago

I solved this separately somehow; beause in the end, I was upgrading to 3.4.1+ to fix the SSL issues, which it did. But they're now gone at the moment using 3.4.0. Not sure why tho. :thinking:

My guess is that the dependencies are now cached locally so lando does not need to fetch them from Debian.org

EDIT: I mis-read your post. You are saying platform ssl is working for you now on 3.4.0. That is odd.

I changed my machine DNS server to 8.8.8.8 from Xfinity's dns and was able to get my lando project to rebuild.

philltran commented 3 years ago

Looks like my browser is registering the cert for ftp.us.debian.org is invalid.

Screen Shot 2021-10-08 at 1 00 42 PM

Screen Shot 2021-10-08 at 1 03 49 PM

mttkng commented 3 years ago

Okay. Bit more info. If you lando destroy and then lando start, when it gets to Manually Installing DPKG... it successfully resolves the domain where lando rebuild would fail at that point.

Manually Installing DPKG...
--2021-10-11 09:25:20--  http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... 64.50.233.100, 64.50.236.52, 208.80.154.15, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|64.50.233.100|:80... connected.
HTTP request sent, awaiting response... 200 OK

However, instead it fails further down the line at Manually Installing gcc-6-base, libc6, & libgcc1...

Manually Installing gcc-6-base, libc6, & libgcc1...
--2021-10-11 09:28:41--  http://ftp.us.debian.org/debian/pool/main/g/gcc-6/gcc-6-base_6.3.0-18+deb9u1_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'ftp.us.debian.org'
ERROR ==> wget: unable to resolve host address 'ftp.us.debian.org'`

thasmo commented 3 years ago

Getting the same issue now when using lando start on 3.4.3

Creating project_app_1 ... done
Manually Installing DPKG...
converted 'http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb' (ANSI_X3.4-1968) -> 'http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb' (UTF-8)
--2021-10-13 08:06:37--  http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... failed: Name or service not known.
wget: unable to resolve host address 'ftp.us.debian.org'
ERROR ==> wget: unable to resolve host address 'ftp.us.debian.org' 
Creating project_solrsearch_1 ... done

Is this something platform.sh has to fix in their images or something?

chris-archer-whisky commented 3 years ago

Okay. Bit more info. If you lando destroy and then lando start, when it gets to Manually Installing DPKG... it successfully resolves the domain where lando rebuild would fail at that point.

Manually Installing DPKG...
--2021-10-11 09:25:20--  http://ftp.us.debian.org/debian/pool/main/d/dpkg/dpkg_1.18.25_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... 64.50.233.100, 64.50.236.52, 208.80.154.15, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|64.50.233.100|:80... connected.
HTTP request sent, awaiting response... 200 OK

However, instead it fails further down the line at Manually Installing gcc-6-base, libc6, & libgcc1...

Manually Installing gcc-6-base, libc6, & libgcc1...
--2021-10-11 09:28:41--  http://ftp.us.debian.org/debian/pool/main/g/gcc-6/gcc-6-base_6.3.0-18+deb9u1_amd64.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'ftp.us.debian.org'
ERROR ==> wget: unable to resolve host address 'ftp.us.debian.org'`

This for me did not work, I just downgrade lando then re-upgrade as a current work around

sryanb commented 3 years ago

Also having this issue on lando v3.4.3. Downgraded to v.3.3.2 and back up and running for now.

ssssct commented 3 years ago

Downgrading to 3.4.0 allowed be to start the project. But afterwards I couldn't lando pull because of the ssl cert being expired.

Same here, looks like we're stuck in a loop. Did you find a workaround? EDIT: Going back and forth between 3.4.0 and 3.4.3 like @chris-archer-whisky mentioned allows to work.

tylers-username commented 3 years ago

I was hoping to help out a bit here. But I can't reproduce this when cloning the Lando repo and testing the bin/lando.js directly.

lando destroy -y && lando start will throw the error
alias landodev=/local/path/bin/lando.js followed by: landodev destroy -y && landodev start does not throw the error. It connects to the debian server as expected.

Where lando version is 3.4.3 and landodev version is 3.4.3

The error is triggered by this line in the production build.

pirog commented 3 years ago

To anyone still experiencing this i would try out https://github.com/lando/lando/releases/tag/v3.5.0

we now have the platform.sh plugin in a separate repo and it is running A LOT of tests, none of which seem to error on this: https://github.com/lando/platformsh/actions

xaqrox commented 3 years ago

v3.5.0 WORKS! All green build and successful pull. Thanks @pirog!

thasmo commented 3 years ago

Resolving ftp.us.debian.org seems to work with 3.5.0. 👍

reynoldsalec commented 3 years ago

Sounds like we should close out this issue but may need to pay attention to lando/platformsh#23 as a follow-up.

lando / platformsh

platform.sh - lando rebuild - Resolving ftp.us.debian.org (ftp.us.debian.org)... failed #25