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
A docker-compose file doesn't require a top-level name field, but when using a nameless file as input to podlet compose --pod, the following error message appears:
[root@digitalocean ztnet]# podlet compose --pod
Error:
0: error converting compose file
1: `name` is required when using `--pod`
Location:
src/cli/compose.rs:130
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
That error message doesn't specify that name is a field in the docker compose file, which I think should also be updated for clarity, but I would also prefer if I could simply provide the name of the pod on the command line so that I could use unmodified compose files as input
The text was updated successfully, but these errors were encountered:
+1, i spent a good amount of time wondering why podlet compose --pod compose.yml wasn't working, and why adding --name to the podlet command didn't help
A docker-compose file doesn't require a top-level name field, but when using a nameless file as input to
podlet compose --pod
, the following error message appears:That error message doesn't specify that
name
is a field in the docker compose file, which I think should also be updated for clarity, but I would also prefer if I could simply provide the name of the pod on the command line so that I could use unmodified compose files as inputThe text was updated successfully, but these errors were encountered: