Lando pull from pantheon multidev not working - lando

I have installed lando and docker-ce, cloned project from Pantheon and trying to
lando pull --database=dev --files=dev --code=dev
after I choose Pantheon account with valid machine key and see this log
Attempting to login via terminus...
[notice] Logging in via machine token.
[error] HTTP request has failed with error "Maximum retry attempts reached".
[error] Could not find a saved token identified by .
[error] Please visit the dashboard to generate a machine token: https://dashboard.pantheon.io/machine-token/create/USER_ID
I am sure that machine key is valid, because if I try to run
terminus auth:login --email=EMAIL
I see
[notice] Logged in via machine token.
My environment:
WSL2 (Focal)
Docker version 20.10.9, build c2ea9bc
Lando v3.6.4
Terminus 3.1.0
PHP 8.1.13

The problem was solved via uninstalling docker-ce from WSL2 and installing Docker Desktop on Host machine (check "Use the WSL 2 based engine). After that, everything works perfectly.

Did you first run the following?
lando init --source=pantheon <-- this should match up your machine token
lando start
Then run lando pull?
Resource: https://pantheon.io/docs/guides/lando-wordpress#installing-wordpress-using-the-pantheon-recipe

Related

docker build is not able to connect to http server even though it is accessible on the command line

We have a Dockerfile that contains a command of the form
RUN dotnet restore --no-cache -s http://localhost:8081/repository/nuget-hosted/
When we run
docker build .
The error encountered at this line is
Retrying 'FindPackagesByIdAsyncCore' for source 'http://localhost:8081/repository/nuget-repo-name/FindPackagesById()?id='Package.Name''.
An error occurred while sending the request.
Couldn't connect to server
/usr/share/dotnet/sdk/2.1.101/NuGet.targets(104,5): error : Failed to retrieve information about 'Package.Name' from remote source 'http://localhost:8081/repository/nuget-repo-name/FindPackagesById()?id='Package.Name''.
However, when we run this same command on the command line, the dotnet restore is successful.
The nuget server in question is running on the same machine. If we hit the same URL in the browser, it is a success.
How do we make the nuget server running at localhoat:8081 accessible within docker build so that the docker image gets created successfully?
As mentioned by https://stackoverflow.com/users/1080064/tkausl replacing http://localhost:8081/repository/nuget-hosted/ with http://1.2.3.4:8081/repository/nuget-hosted/ where 1.2.3.4 is the actual ip address solved the issue.

Using On-Perm Artifactory as a docker registry while behind the Azure Application Proxy

Artifactory 6.0.1 PRO
$ docker --version
Docker version 18.03.1-ce, build 9ee9f40
We have setup artifactory with several docker instances. We do have SSO enabled to our SAML authentication system but now we cannot seem to login to the docker instance:
I do have DOCKER_OPTS=" --insecure-registry"
$ docker login artifactory.foo.internal
Username: admin
Password:
Error response from daemon: Get https://artifactory.foo.internal/v2/: unknown: Unsupported docker repository request for 'v2'
No matter what I use in username/password I get the same error.
I have also tried using artifactory.foo.internal:443
We're using Tomcat as a direct connection. Docker configuration is set to PATH.
Any suggestions would be greatly appreciated.

Cloud foundry SSH not working

I am not able to make SSH working.
I checked that SSH is enable on the Application and Space level.
But when i ran
cf ssh "MY-APP-NAME" i get the following error:
FAILED
Error: SSH session allocation failed: ssh: unexpected packet in response to
channel open: <nil>
I also tried to connect without CLi and using the command
ssh -p 2222 cf:abcdefab-1234-5678-abcd-1234abcd1234/0#ssh.MY-DOMAIN.com
But when i entered the password the server stopped the connection (i used Putty).
I am trying to access with SSH because i need to launch npm install to install the dependencies of my application.
Thank you for your help
There is no need to ssh into an app to install dependencies.
Please have a look at Swisscoms Getting Started Guide for Node.js:
https://docs.developer.swisscom.com/tutorial-nodejs/index.html
The section 'Declare App Dependencies' (https://docs.developer.swisscom.com/tutorial-nodejs/dependencies.html) shows you how you specify the dependencies in a file called 'package.json'. This will then be automatically installed by the nodejs buildpack (https://github.com/cloudfoundry/nodejs-buildpack).

Jenkins CI - SSL CA error

NOTE: This is .NET Core on Linux (Ubuntu)
I am setting up some CI infrastructure for .NET Core code and am running into a strange issue. Specifically, when it comes to package restore (dotnet restore).
The Jenkins instance that I am running is hosted on Azure via a Bitnami Jenkins image. In my build, I have a number of build steps. One of them (the one that actually triggers dotnet restore) is an Execute Shell.
When I run whoami from it, I get that I am the user tomcat. When dotnet restore is triggered from within the build step, however, I get the following error:
06:22:37 log : Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/system.runtime.serialization.primitives/index.json'.
06:22:37 log : An error occurred while sending the request.
06:22:37 log : Problem with the SSL CA cert (path? access rights?)
That same issue does not happen if I SSH into the box and do a sudo su - tomcat - running dotnet restore on the same folder from a SSH session works, while doesn't work in the Execute Shell step (despite the fact that both run in the same user context).
What am I missing that might be causing this?

Gitlab registry...unable to login not running?

Followed the gitlab-registry guide to get it running (and enabled to project)
I know the HTTPS works fine (TLS via letsencrypt) because when i login to my gitlab, it successfully redirects to https.
when attempting to login to docker however:
docker login (my domain)
i am getting:
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
netstat -tulpn shows that registry running on 4567
but completely unable to connect to it
You need to have docker installed on the machine you are running docker login from. And if it's installed, you need to be root or in the docker group.

Resources