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
Copy file name to clipboardExpand all lines: docs/faq.md
+4-27Lines changed: 4 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,32 +113,15 @@ services:
113
113
- This message is displayed when you run `defang compose up` and the Compose file declares a `build` with a `context` that contains more than 10 files. Ensure the context refers to the correct folder. Defang will use the `context` as is, but you may experience slow build times. If you want to speed up the build, you should reduce the number of files in the `context`.
114
114
115
115
### "AWS provider was selected, but AWS environment variables are not set"
116
-
- This message is displayed when you run `defang compose up` with the `--provider=aws` but none of the AWS environment variables were not set. If you proceed, the deployment might fail.
116
+
- This message is displayed when you run `defang compose up` with the `--provider=aws` but none of the AWS environment variables were set. If you proceed, the deployment might fail, unless you have defined defined `default` credentials in the AWS configuration files or are running on an AWS instance.
117
117
118
118
### "Using Defang provider, but AWS environment variables were detected"
119
119
- This message is displayed when you run `defang compose up` with the `--provider=defang` but AWS environment variables were detected. The AWS environment variables will be ignored.
120
120
121
-
### "secret … is not defined in the top-level secrets section"
122
-
- This message is displayed when you run `defang compose up` and the Compose file declares a `secret` that is not defined in the top-level `secrets` section. To silence the warning, define the secret in the top-level `secrets` section:
123
-
```
124
-
services:
125
-
service1:
126
-
…
127
-
secrets:
128
-
- my_secret
129
-
secrets:
130
-
my_secret:
131
-
external: true
132
-
```
121
+
## Errors
133
122
134
-
### "unsupported secret …: not marked external:true"
135
-
- This message is displayed when you run `defang compose up` and the Compose file declares a `secret` that is not marked `external:true`. Defang only supports external secrets, managed by the `defang config` command. To silence the warning, mark the secret as `external:true` in the top-level `secrets` section:
136
-
```
137
-
…
138
-
secrets:
139
-
my_secret:
140
-
external: true
141
-
```
123
+
### "Stack:… is in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state and cannot be updated"
124
+
- This happens if different version of the Defang CLI are used with the same AWS account. Each version one will try to update the CD stack to its version, back and forth. Make sure that all users have the same version of the CLI. Check the CLI version using `defang version`.
142
125
143
126
### "invalid healthcheck: ingress ports require an HTTP healthcheck on `localhost`.
144
127
@@ -167,9 +150,3 @@ secrets:
167
150
healthcheck:
168
151
test: ["CMD", "./my-healthcheck"]
169
152
```
170
-
171
-
172
-
## Errors
173
-
174
-
### "Stack:… is in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state and cannot be updated"
175
-
- This happens if different version of the Defang CLI are used with the same AWS account. Each version one will try to update the CD stack to its version, back and forth. Make sure that all users have the same version of the CLI. Check the CLI version using `defang version`.
0 commit comments