coder / coder/envbuilder

envbuilder don't recognize "dockerComposeFile" param

Offen
#107 1 Kommentar 7 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Go
Sterne
300
Forks
64
Ø Merge
20 Min.
Gemergte PRs (30 T.)
1

Beschreibung

Hi! My devcontainer.json looks like this:

```json
{
"name": "keycrm",
"dockerComposeFile": [
"../example.docker-compose.yml"
],
"service": "app",
"services": ["app", "db"],
"forwardPorts": [80],
"postAttachCommand": "service apache2 start",
"extensions": [
"felixfbecker.php-pack",
"cweijan.vscode-mysql-client2"
]
}
```

and coder don't recognize "dockerComposeFile" option. It's described in devcontainer.json schema, and supported by my IDE (phpstorm) as well. But when I'm trying to create a workspace with such devcontainer it usually fallback to default image.
So, maybee in future, would envbuilder support docker-compose files to build, or I'm using it in wrong way? I'm trying to make developer's workspace with standalone environment, but creating only "app" is not enough in case of no DB.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start with the supplied devcontainer.json and ../example.docker-compose.yml, then trace how envbuilder handles the dockerComposeFile option versus its default image path. Define whether the app and db services should be built and started, and verify that a workspace using this configuration no longer falls back to the default image.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
docker-compose
Bereich
devops
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.