-
Notifications
You must be signed in to change notification settings - Fork 55
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
Docker_Task on MacOS Project Name Issue #3248
Comments
The "project" name is by default set to the folder's name, which is not always compatible. To fix that issue, the name of the project has to be specified through environmental variables (export COMPOSE_PROJECT_NAME=myproject) or at runtime: |
@laugimethods Thank you for reporting this issue. A fast workaround is to change the docker-compose command in the With the current functionality we cannot overwrite environment variables, because all variables are injected by proactive with prefix. Imho an interestting solution is to allow the user to specify docker-compose arguments as Generic Information. |
@tobwiens Whatever is the solution, the provided workflows have to behave as expected right away...
or
|
Take note that the |
@laugimethods Thank you for adding further information. |
Using Docker Version 18.05.0-ce-mac67 (25042) - Edge, the provided script_docker workflow fails:
[[email protected];09:53:08] Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.
[[email protected];09:53:08] To deploy your application across the swarm, use docker stack deploy.
[[email protected];09:53:08] Creating -50782672helloworld_1 ...
[[email protected];09:53:08] �[1A�[2K
[[email protected];09:53:08] Creating -50782672_helloworld_1 ... �[31merror�[0m
[[email protected];09:53:08] �[1B
[[email protected];09:53:08] ERROR: for -50782672_helloworld_1 Cannot create container for service helloworld: b'Invalid container name (-50782672_helloworld_1), only [a-zA-Z0-9][a-zA-Z0-9.-] are allowed'
The text was updated successfully, but these errors were encountered: