-
-
Notifications
You must be signed in to change notification settings - Fork 652
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]: Running 2/5t of type volume
should not define bind
option
#984
Comments
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you already looked into this bug?
(Optional) Error message
[+] Running 2/5t of type
volume
should not definebind
optionWhat went wrong?
Starting services...
[+] Running 0/0
This message has started showing up when I start containers. I haven't been able to find anything that would point me as to what happened to cause it.
Expected behaviour
Containers should start with no messages.
How can we reproduce the bug?
Not sure. This is my startup script:
Host Operating System
Linux
Host Platform (amd64, arm64, other)
amd64
(Linux only) Is SELinux enabled?
Yes, SELinux is enabled
Docker version
Docker version 23.0.5, build bc4487a
Docker Compose version
Docker Compose version v2.17.3
Devilbox version
Devilbox v3.0.0-beta-0.3 (2023-01-02)
Have you removed stopped containers before starting?
Yes
Have you pulled latest Docker images before starting?
Yes
Devilbox start command
See above script
Config: .env file
(Optional) Additional information
No response
The text was updated successfully, but these errors were encountered: