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
For setting up the Magento 2 instance with warden, we are only specifying the Magepack to enabled by setting flag as 1. On running warden env config the image pulled is shown to be image: docker.io/wardenenv/magepack:2.3. But if I run warden env exec -u 0 magepack sh, get into magepack shell and run magepack -v the version is shown as 2.8.0.
Version of Warden
Warden version in-dev
Operating System and Installation Method
Ubuntu 20.04
Image
magepack
Describe the Bug
For setting up the Magento 2 instance with warden, we are only specifying the Magepack to enabled by setting flag as 1. On running
warden env config
the image pulled is shown to beimage: docker.io/wardenenv/magepack:2.3
. But if I runwarden env exec -u 0 magepack sh
, get into magepack shell and run magepack -v the version is shown as 2.8.0.Expected Behavior
So when warden is enabled with magepack, it should pull the latest 2.11 version as available here https://hub.docker.com/r/wardenenv/magepack/tags
Additional context
No response
The text was updated successfully, but these errors were encountered: