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
The very first time the workspace is built and the workspace image is craeted then whatever value is set for the install for phpmyadmin in starter.ini will be respected. However on subsequent creations of the gitpod workspace this phpmyadmininstall value will only be respected if the workspace image is rebuilt. The workspace image is cached and will only rebuild if there is a significant change to the .gitpod.Docker file.
Screenshots
Steps to reproduce
Set the install value for phpmyadmin in starter.ini to 1. Push that change to your repository.
Create a Gitpod workspace from your repository for the very first time.
phpmyadmin is successfully installed
Set the install value for phpmyadmin in starter.ini to 0. Push that change to your repository.
Create another Gitpod workspace from your repository.
phpmyadmin is still installed.
Expected behavior
When the install value for phpmyadmin in starter.ini is set to 0 and the a new Gitpod workspace is created then phpmyadmin should not be installed.
Workaround
You can workaround this issue by incrementing the value of ENV INVALIDATE_CACHE in .gitpod.Dockerfile. This will force the build of a new workspace image.
The text was updated successfully, but these errors were encountered:
Use the workaround when creating multiple new workspaces and chaning the phpmyadmin install directive in between. This is result of the docker caching mechanism within the gitpod system.
Workspaces are cached, so unless a workspace image is forced to be rebuilt then there is guarantee that phpmyadmin will be installed or not.
It appears that when a workspace is created in gitpod from a repo for the very first time, the workspace image is built, not cached.
Regardless if you are creating new workspaces and changing the phpmyadmin install directive in starter.ini, in between creation of these workspaces then you will need to increment the value of ENV INVALIDATE_CACHE in .gitpod.Dockerfile and save it to the repository before you create the workspace to ensure that you get your desired results.
Describe the bug
The very first time the workspace is built and the workspace image is craeted then whatever value is set for the
install
forphpmyadmin
instarter.ini
will be respected. However on subsequent creations of the gitpod workspace thisphpmyadmin
install
value will only be respected if the workspace image is rebuilt. The workspace image is cached and will only rebuild if there is a significant change to the.gitpod.Docker
file.Screenshots
Steps to reproduce
install
value forphpmyadmin
instarter.ini
to1
. Push that change to your repository.phpmyadmin
is successfully installedinstall
value forphpmyadmin
instarter.ini
to0
. Push that change to your repository.phpmyadmin
is still installed.Expected behavior
When the
install
value forphpmyadmin
instarter.ini
is set to0
and the a new Gitpod workspace is created thenphpmyadmin
should not be installed.Workaround
You can workaround this issue by incrementing the value of
ENV INVALIDATE_CACHE
in.gitpod.Dockerfile
. This will force the build of a new workspace image.The text was updated successfully, but these errors were encountered: