You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Lando rebuild command, when run on a project with local docker tags referenced in the docker-compose file, will error out trying to pull the image - but it will Lando start fine...
e.g. docker tag uselagoon/mariadb-drupal:latest lagoon/mariadb-drupal:latest
replace the mariadb image in the docker-compose.yml and lando rebuild to see the error
ERROR: for mariadb pull access denied for lagoon/mariadb-drupal, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
It seems as if Lando is trying to pull the image direct from docker hub, as opposed to seeing it exists locally.
Given the specificity of the integration, this is most very limited in it's scope, but it does hamper local testing.
The text was updated successfully, but these errors were encountered:
This has just bitten me badly, as several of my stack's Dockerfiles reference the local cli image which is built first, and so the lando start fails to build those other images 😭
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues.
A
Lando rebuild
command, when run on a project with local docker tags referenced in the docker-compose file, will error out trying to pull the image - but it willLando start
fine...e.g.
docker tag uselagoon/mariadb-drupal:latest lagoon/mariadb-drupal:latest
replace the mariadb image in the docker-compose.yml and lando rebuild to see the error
It seems as if Lando is trying to pull the image direct from docker hub, as opposed to seeing it exists locally.
Given the specificity of the integration, this is most very limited in it's scope, but it does hamper local testing.
The text was updated successfully, but these errors were encountered: