How to reuse service image when opening a project with devcontainer-cli? - ruby-on-rails

Question

I'm looking for a way to make the "devcontainer open ." command to finish faster. I was looking at the log produced by that command and I noticed something:
[1895 ms] Start: Run: docker-compose --project-name hobby-on-rails -f /home/pedro/tempo-livre/hobby-on-rails/docker-compose.yml build
That got me wondering, I expected the build to run only once, like when you run docker-compose up, and not every time I start the project. I think I'm missing some configuration to tell the devcontainer that it's not necessary to build my web service again. Let's take a look at my devcontainer.yml:
// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
// https://github.com/microsoft/vscode-dev-containers/tree/v0.234.0/containers/docker-existing-docker-compose
// If you want to run as a non-root user in the container, see .devcontainer/docker-compose.yml.
{
"name": "Hobby On Rails",
// Update the 'dockerComposeFile' list if you have more compose files or use different names.
// The .devcontainer/docker-compose.yml file contains any overrides you need/want to make.
"dockerComposeFile": [
"../docker-compose.yml"
],
// The 'service' property is the name of the service for the container that VS Code should
// use. Update this value and .devcontainer/docker-compose.yml to the real service name.
"service": "web",
// The optional 'workspaceFolder' property is the path VS Code should open by default when
// connected. This is typically a file mount in .devcontainer/docker-compose.yml
"workspaceFolder": "/opt/hobbyonrails",
// Set *default* container specific settings.json values on container create.
"settings": {},
// Add the IDs of extensions you want installed when the container is created.
"extensions": [
"castwide.solargraph",
"github.copilot",
"misogi.ruby-rubocop"
]
// Use 'forwardPorts' to make a list of ports inside the container available locally.
// "forwardPorts": [],
// Uncomment the next line if you want start specific services in your Docker Compose config.
// "runServices": [],
// Uncomment the next line if you want to keep your containers running after VS Code shuts down.
// "shutdownAction": "none",
// Uncomment the next line to run commands after the container is created - for example installing curl.
// "postCreateCommand": "apt-get update && apt-get install -y curl",
// Uncomment to connect as a non-root user if you've added one. See https://aka.ms/vscode-remote/containers/non-root.
// "remoteUser": "vscode"
}
The service web is being build every time. Is it possible to prevent this from happening?
In case you would like to take a look at my docker-compose.yml:
version: "3.7"
services:
db:
image: postgres:14.4
container_name: hobbyonrails_db
ports:
- 5432:5432
env_file:
- ./.docker/env_files/.env
healthcheck:
test: ["CMD-SHELL", "pg_isready"]
interval: 10s
timeout: 5s
retries: 5
volumes:
- ./.docker/volumes/postgres_data:/var/lib/postgresql/data
web:
image: hobbyonrails
container_name: hobbyonrails_web
env_file:
- ./.docker/env_files/.env
build:
context: .
depends_on:
db:
condition: service_healthy
links:
- db
ports:
- 3000:3000
volumes:
- .:/opt/hobbyonrails:cached
stdin_open: true
tty: true
livereload:
image: hobbyonrails
container_name: hobbyonrails_livereload
depends_on:
- web
ports:
- 35729:35729
command: ["bundle", "exec", "guard", "-i"]
env_file:
- ./.docker/env_files/.env
volumes:
- .:/opt/hobbyonrails:cached
tailwindcsswatcher:
image: hobbyonrails
container_name: hobbyonrails_tailwindcsswatcher
depends_on:
- web
ports:
- 3035:3035
command: ["bin/rails", "tailwindcss:watch"]
env_file:
- ./.docker/env_files/.env
volumes:
- .:/opt/hobbyonrails:cached
tty: true
selenium:
container_name: hobbyonrails_selenium
image: selenium/standalone-chrome:3.141.59
ports:
- 4444:4444
volumes:
postgres_data:
What do you think?