Skip to content
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.

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

[Bug]: the location of the Docker Compose file cannot be specified #2239

Closed
Yurgeman opened this issue May 17, 2024 · 3 comments · Fixed by #2311
Closed

[Bug]: the location of the Docker Compose file cannot be specified #2239

Yurgeman opened this issue May 17, 2024 · 3 comments · Fixed by #2311

Comments

@Yurgeman
Copy link

Yurgeman commented May 17, 2024

Description

when creating a New Resource from Git (build pack - Docker Compose), it is not possible to specify the location of the Docker Compose file

watch the video:

composeName.mp4

Minimal Reproduction (if possible, example repository)

  1. click New resource
  2. Select Public Repository
  3. add https://github.com/taigaio/taiga-docker or use main branch
  4. select build pack - Docker Compose
  5. change docker-compose.yaml to docker-compose.yml (docker-compose.yml)
  6. see error

Exception or Error

Error messages:
Docker Compose file not found at: /docker-compose.yaml
or
Mapping values are not allowed in multi-line blocks at line 4 (near "&default-back-environment").

Version

v4.0.0-beta.283

@craigharman
Copy link

craigharman commented May 27, 2024

Same for me, been happening for months. Anything that can be done about this as it means I can't use docker-compose deployments. Any work arounds or quick fixes?

Similar to, if not the same as: #2142

@jvdboog
Copy link

jvdboog commented May 29, 2024

My docker-compose file has the .yaml extension and even then it's not working... Is there any workaround for this?

@andrasbacsai
Copy link
Member

I found the issue. Are you using a non-root user, right, @jvdboog?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants