I had 2 more ideas this morning.
1. Check the GitHub for any other docker-compose.yml examples. None are maintained here...
2. Try to lower the directory target of the volume (container side). Doing so resulted in this error for both containers:


Error: Server: (failed to OpenDefault), Wrapped: (failed to defaultPath), failed to ConfigDir: Can't continue. We can't safely access "/home/opuser/.op" because it's not owned by the current user. Change the owner or logged in user and try again.


So, I haven't gotten any further than the original post.

Oh, I found docker-compose.yaml on https://github.com/1Password/connect/blob/main/examples/docker/compose/docker-compose.yaml. Man, I still will never understand why we settled on 2 file extensions for the same language.

Anyway, there's no commit history so it's been this way for ages and somehow I don't see others having the same issue deploying a similar config, so still wondering if others have any idea what's causing the problem.

For kicks and giggles I spun this up on Docker Desktop for Windows, and quickly got the configuration working. So, something must be wrong with my Amazon_Linux configuration. I can try rebuilding this machine to see if the error occurs again. In the meantime, I'll post my configs in case someone else would like to try replicating the issue.

Terraform Config:
```

Terraform HCL

provider "aws" {
region = "us-east-1"
shared_credentials_file = "~/.aws/credentials"
profile = "default"
}

resource "aws_security_group" "onepassword_connect_api" {
name = "onepassword_connect_api"
description = "Allow 8080 traffic into 1password API"

ingress = [
{
description = "API"
from_port = 8080
to_port = 8080
protocol = "tcp"
cidr_blocks = ["/32"]
ipv6_cidr_blocks = []
prefix_list_ids = []
self = false
security_groups = []
}
]

egress = [
{
description = "any"
from_port = 0
to_port = 0
protocol = "-1"
cidr_blocks = ["0.0.0.0/0"]
ipv6_cidr_blocks = []
prefix_list_ids = []
self = false
security_groups = []
}
]

tags = {
Name = "onepassword_connect_api"
name = "onepassword_connect_api"
}
}

resource "aws_instance" "use1vl1pc" {
ami = "ami-087c17d1fe0178315"
instance_type = "t2.micro"
availability_zone = "us-east-1d"
key_name = ""

vpc_security_group_ids = [
"",
"${aws_security_group.onepassword_connect_api.id}"
]

tags = {
name = "use1vl1pc"
description = "1Password Connect server, allows our applications to use 1Password Vaults"
Name = "use1vl1pc"
project = "internal"
}
}

resource "aws_eip" "use1vl1pc_EIP" {
instance = "${aws_instance.use1vl1pc.id}"
vpc = true
tags = {
name = "use1vl1pc_EIP"
ec2Target = "use1vl1pc"
project = "internal"
}
}
```

There you can see the AMI I'm using if you just want to build it manually. Then I run a shell script because I'm still working on Configuration Management for this company.

1password_connect_setup.sh
```

!/bin/bash

sudo yum update -y

sudo yum install -y tmux yum-utils git

install Docker Engine, Amazon Linux 2

sudo amazon-linux-extras install -y docker
sudo systemctl enable docker && sudo systemctl start docker
if groups | grep -q docker; then
echo "ec2-user is already part of the docker group"
else
echo "adding ec2-user to docker group"
sudo usermod -aG docker ec2-user && sudo su - ec2-user #enable ec2-user to use docker without sudo
fi

sudo docker run hello-world #test if docker runs ok

install docker-compose Amazon Linux 2

sudo curl -L https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m) -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
docker-compose version

install 1password connect

mkdir -p ~/1pass
cd ~/1pass
# add something here to download the repository
docker-compose up -d
```

In the Docker Compose example config that we've published, we're using the Docker Compose feature to specify files as volumes (i.e. the 1password-credentials.json file). There's a small downside of that approach though, and is that if the file is not present or can't be found for whatever reason, Docker Compose won't fail, but will just continue and interpret the specified file as a directory instead.

So you'll have to make sure the 1password-credentials.json file is in the very same directory where you're running docker-compose up from. (And I don't see anything in your script around the credentials file, but maybe that's in the part you left out?)