-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
named docker volume doesn't work anymore with 0.9.0 #5562
Comments
Hey @MorphBonehunter, Sorry about this, it looks to be a regression in how we handle generating container binds in While we figure out the correct fix, it should be possible for you to work around this by using the task "test" {
driver = "docker"
config {
image = "redis:3.2"
mounts = [
{
type = "volume"
target = "/testing"
source = "test"
},
]
} |
Thanks for your suggestion @dantoml, this is working for me. |
As this was an unintentional backward compatibility break we intend to restore the 0.8.7 behavior in Nomad 0.9.1. We still recommend using |
hey @schmichael should ne no problem to use the |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.8.7 (21a2d93eecf018ad2209a5eab6aae6c359267933+CHANGES)
Nomad v0.9.0 (18dd59056ee1d7b2df51256fe900a98460d3d6b9)
Operating system and Environment details
ArchLinux
Issue
After upgrading to nomad 0.9.0 named docker volumes are not working anymore.
Reproduction steps
Job file (if appropriate)
In nomad 0.9.0 the same job result not in an volume mount but an bind mount.
The text was updated successfully, but these errors were encountered: