You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, ive been facing an issue with the relative path of a dockerfile, when i run my configuration i get Dockerfile found, assuming ECR pipeline from mu but right after it fails with the message func1 ▶ ERROR Error response from daemon: Cannot locate specified Dockerfile: Dockerfile
will be sending in a pull request for the bugfix soon:
Version of mu: 1.5.10
Platform (Linux, OS X, Windows): Linux (Ubuntu 18.04)
The complete mu.yml file used:
namespace: gigi
environments:
- name: staging
provider: ecs-fargate
cluster:
keyName: bastionhost
service:
port: 80
pathPatterns:
- /*
healthEndpoint: /
# What namespace to use for service discovery (default <environment>.<namespace>.local)
name: docs
desiredCount: 2
dockerfile: ./docker/docs/Dockerfile
protocol: HTTP
targetCPUUtilization: 50
minSize: 1
maxSize: 4
deploymentStrategy: rolling
environment:
ENV: staging
PORT: 80
The complete command that was executed: mu -p gigi-staging service push -t v0.0.1
Any output from the command:
Dockerfile found, assuming ECR pipeline
Upsert repo for service 'docs'
Updated stack 'gigi-repo-docs'
Building service:'docs' as image:632223924262.dkr.ecr.ap-southeast-1.amazonaws.com/gigi-docs:v0.0.1'
func1 ▶ ERROR Error response from daemon: Cannot locate specified Dockerfile: Dockerfile
func1 ▶ ERROR
Details of the expected results and how they differed from the actual results:
Dockerfile should be possible to be built from a relative path, it doesnt.
Hi, ive been facing an issue with the relative path of a dockerfile, when i run my configuration i get
Dockerfile found, assuming ECR pipeline
from mu but right after it fails with the messagefunc1 ▶ ERROR Error response from daemon: Cannot locate specified Dockerfile: Dockerfile
heres my config:
any help is appreciated.
thanks
The text was updated successfully, but these errors were encountered: