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
{{ message }}
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.
If the user does not purge the containers (eq using the --epheremal or the new --fresh flag) between launches of Bee Factory and then wants to upgrade to new versions of containers Bee Factory will error out as the container's image won't be as expected. For now, the workaround is to use the --fresh flag when updating image versions, which will purge the containers before the launch, but a better UX alternative would be to prompt the user for confirmation if the image should be purged and then continue with start-up of the cluster.
The text was updated successfully, but these errors were encountered:
If the user does not purge the containers (eq using the
--epheremal
or the new--fresh
flag) between launches of Bee Factory and then wants to upgrade to new versions of containers Bee Factory will error out as the container's image won't be as expected. For now, the workaround is to use the--fresh
flag when updating image versions, which will purge the containers before the launch, but a better UX alternative would be to prompt the user for confirmation if the image should be purged and then continue with start-up of the cluster.The text was updated successfully, but these errors were encountered: