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
ERROR: unknown: Tag 2.6.66 was deleted or has expired. To pull, revive via time machine
rake aborted!
Command failed with status (1): [docker-compose up -d tower...]
lib/tasks/service.rake:190:in start' lib/tasks/service.rake:7:in call'
lib/tasks/service.rake:7:in block (2 levels) in <top (required)>' lib/tasks/service.rake:198:in block (2 levels) in <top (required)>'
lib/tasks/service.rake:285:in start' lib/tasks/service.rake:7:in call'
lib/tasks/service.rake:7:in block (2 levels) in <top (required)>' lib/tasks/service.rake:302:in block (2 levels) in <top (required)>'
/home/app/.rvm/gems/ruby-2.6.6/gems/rake-13.0.1/exe/rake:27:in <top (required)>' /home/app/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:22:in eval'
/home/app/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:22:in `
'
Tasks: TOP => service:tower
(See full trace by running task with --trace)
The text was updated successfully, but these errors were encountered:
ERROR: unknown: Tag 2.6.66 was deleted or has expired. To pull, revive via time machine
'rake aborted!
Command failed with status (1): [docker-compose up -d tower...]
lib/tasks/service.rake:190:in
start' lib/tasks/service.rake:7:in
call'lib/tasks/service.rake:7:in
block (2 levels) in <top (required)>' lib/tasks/service.rake:198:in
block (2 levels) in <top (required)>'lib/tasks/service.rake:285:in
start' lib/tasks/service.rake:7:in
call'lib/tasks/service.rake:7:in
block (2 levels) in <top (required)>' lib/tasks/service.rake:302:in
block (2 levels) in <top (required)>'/home/app/.rvm/gems/ruby-2.6.6/gems/rake-13.0.1/exe/rake:27:in
<top (required)>' /home/app/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:22:in
eval'/home/app/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:22:in `
Tasks: TOP => service:tower
(See full trace by running task with --trace)
The text was updated successfully, but these errors were encountered: