Skip to content

fix: prevent nil map panic when docker-compose.yaml has top-level name field #3204

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.

Sign up for GitHub

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

Open
raman1236 wants to merge 1 commit into
base: main
Choose a base branch
from
+14 −0
Open

fix: prevent nil map panic when docker-compose.yaml has top-level name field #3204

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pkg/devspace/compose/manager.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@ func LoadDockerComposeProject(path string) (*composetypes.Project, error) {
Content: composeFile,
},
},
Environment: map[string]string{},
})
if err != nil {
return nil, err
Expand Down
9 changes: 9 additions & 0 deletions pkg/devspace/compose/testdata/named_project/devspace.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
version: v2beta1
name: docker-compose
deployments:
web:
helm:
values:
containers:
- name: web-container
image: nginx:latest
4 changes: 4 additions & 0 deletions pkg/devspace/compose/testdata/named_project/docker-compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
name: myproject
services:
web:
image: nginx:latest