aws_vpc.my_vpc: Still creating... [02m30s elapsed

[doug2901]

Hello everyone!

I'm trying to use Floci to study Terraform with AWS, but I'm having problems creating a VPC. Here is how I'm working with it:

Floci env:

docker run -d \
  -p 4566:4566 \
  -p 5100-5199:5100-5199 \
  -p 6379-6399:6379-6399 \
  -p 7001-7099:7001-7099 \
  -e QUARKUS_LOG_LEVEL=DEBUG \
  hectorvent/floci:latest

Terraform file

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "6.40.0"
    }
  }
}

# Configure the AWS Provider
provider "aws" {
  region = "us-east-1"
}

resource "aws_vpc" "my_vpc" {
  cidr_block           = "10.0.0.0/16"
  enable_dns_support   = false
  enable_dns_hostnames = false
  tags = {
    Name        = "my_vpc"
    Environment = "dev"
    ManagedBy   = "Terraform"
  }
}

Error

aws_vpc.my_vpc: Still creating... [04m51s elapsed]
aws_vpc.my_vpc: Still creating... [05m01s elapsed]
aws_vpc.my_vpc: Still creating... [05m11s elapsed]
╷
│ Error: creating EC2 VPC: modifying EnableDnsSupport: waiting for completion: output = true, want false
│
│   with aws_vpc.my_vpc,
│   on main.tf line 15, in resource "aws_vpc" "my_vpc":
│   15: resource "aws_vpc" "my_vpc" {
│
╵

Floci logs

2026-04-13 13:46:08,487 DEBUG [io.quarkus.vertx.http.runtime.RoutingUtils] (executor-thread-1) CDI request context owner has changed from 'quarkus-rest' to 'quarkus-rest'

2026-04-13 13:46:08,489 DEBUG [io.github.hectorvent.floci.core.common.AwsQueryController] (executor-thread-1) Query protocol service=ec2 action=DescribeVpcAttribute

2026-04-13 13:46:08,489 DEBUG [io.github.hectorvent.floci.services.ec2.Ec2QueryHandler] (executor-thread-1) EC2 action: DescribeVpcAttribute

Terraform version

Terraform v1.14.8
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v6.40.0

Anyone know a fix for this?

[hectorvent]

Hi @doug2901,

Thanks for reporting this. I created an issue from this discussing #468

Thank you again!

[hectorvent]

@doug2901 is this something you can validate? In the latest floci docker image

[hectorvent]

Thanks, I will work with those new issues this week.

[hectorvent]

Could you try to disable EC2 docker instance creation?

FLOCI_SERVICES_EC2_MOCK=true

The docker socket is not mounted.

[doug2901]

the error changed

╷
│ Error: reading EC2 Instance (i-4426ae762893f6853) launch template: reading EC2 Instance (i-4426ae762893f6853) launch template ID tag: too many results: wanted 1, got 3
│
│   with aws_instance.my_instance,
│   on main.tf line 67, in resource "aws_instance" "my_instance":
│   67: resource "aws_instance" "my_instance" {

[hectorvent]

PR #706 should resolved it.

[hectorvent]

could you try the image floci/floci:nightly?

docker run -d \
  -p 4566:4566 \
  -p 5100-5199:5100-5199 \
  -p 6379-6399:6379-6399 \
  -p 7001-7099:7001-7099 \
  -e QUARKUS_LOG_LEVEL=DEBUG \
  floci/floci:nightly

[Mohith1612]

@doug2901 @hectorvent I validated this on the current image. It's fixed by #468, which added DescribeVpcAttribute and the other VPC attribute operations.

I used your exact config (Terraform 1.14.8, hashicorp/aws 6.40.0, enable_dns_support = false, enable_dns_hostnames = false) against floci/floci:2.2.0:

aws_vpc.my_vpc: Creation complete after 16s [id=vpc-1a9e9d37]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

$ terraform state show aws_vpc.my_vpc
    enable_dns_hostnames = false
    enable_dns_support   = false

The modifying EnableDnsSupport: waiting for completion: output = true, want false error doesn't happen anymore, because the attribute is now stored and returned correctly.

Two notes:

• The image moved from hectorvent/floci to floci/floci, so pull floci/floci:latest (or pin floci/floci:2.2.0).
• If the provider isn't already pointed at Floci (for example through AWS_ENDPOINT_URL=http://localhost:4566), add this to the provider block:

  access_key                  = "test"
  secret_key                  = "test"
  skip_credentials_validation = true
  skip_requesting_account_id  = true
  endpoints { ec2 = "http://localhost:4566" }