Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeout when pulling the tryretool/backend container #20

Open
Git-on-my-level opened this issue Mar 16, 2023 · 2 comments
Open

Timeout when pulling the tryretool/backend container #20

Git-on-my-level opened this issue Mar 16, 2023 · 2 comments

Comments

@Git-on-my-level
Copy link

I'm specifying a specific version 2.110.5 but I am getting this error in the ECS task that tries to pull the image

CannotPullContainerError: pull image manifest has been retried 5 time(s): failed to resolve ref docker.io/tryretool/backend:2.110.5: failed to do request: Head "https://registry-1.docker.io/v2/tryretool/backend/manifests/2.110.5": dial tcp 34.205.13.154:443: i/o timeout

I have also tried this with the default version but it fails with the same error (different version number of course)

Do you have any insight into why I can't pull the image from ECS? Is this still the right registry to pull from?

These are all the required and optional variables I'm populating:

module "retool_self_hosted" {
  source                                 = "ActionIQ/retool-ecs-fargate/aws"
  retool_licence                         = var.retool_license
  retool_release_version                 = var.retool_release_version
  retool_task_container_force_deployment = var.retool_task_container_force_deployment
  vpc_id                                 = var.vpc_id
  aws_region                             = var.aws_region
  availability_zones                     = var.availability_zones
  retool_alb_subnets                     = var.subnet_ids
  retool_jobs_runner_ecs_service_subnet  = var.subnet_ids
  retool_ecs_service_subnet              = var.subnet_ids
  retool_db_subnet_ids                   = var.subnet_ids
  alb_listener_certificate_arn           = var.alb_listener_certificate_arn
  aws_lb_listener_protocol               = "HTTPS"
  database_name                          = "retool"
  route_53_zone_id                       = var.route_53_zone_id
  retool_custom_host_url                 = var.retool_custom_host_url
  retool_ecs_service_count               = var.retool_ecs_service_count
  retool_jobs_runner_task_cpu            = var.retool_jobs_runner_task_cpu
  retool_jobs_runner_task_memory         = var.retool_jobs_runner_task_memory
  retool_rds_cluster_instance_class      = var.retool_rds_cluster_instance_class
  retool_rds_cluster_instance_count      = var.retool_rds_cluster_instance_count
  retool_task_cpu                        = var.retool_task_cpu
  retool_task_memory                     = var.retool_task_memory
}
@shaun-hysata
Copy link

Hi @Git-on-my-level, I'm also receiving this error. Did you have any luck in fixing/resolving?

Many thanks,

@Git-on-my-level
Copy link
Author

Hi @Git-on-my-level, I'm also receiving this error. Did you have any luck in fixing/resolving?

Many thanks,

If I remember correctly, you can bypass this error by toggling the "assign public IP" property of ECS. If you have time you can open a PR for this repo, I was going to but didn't end up going with self hosted Retool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants