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
{{ message }}
This repository has been archived by the owner on Jun 18, 2022. It is now read-only.
We had a power failure on our servers last night and since then I have noticed some strange behaviour on convoy.
A service could not be started and received the following error message:
create volume_name: Error occurred while checking if volume volume_name exists: EOF
So I tried to delete the volume, but got the following error:
Error deleting volume_name: Error response from server, Volume not found.
ERRO[0000] Error response from server, Volume not found.
{
"Error": "Error response from server, Volume not found.\n"
}
If I now want to create a new volume manually, I get the following message:
ERRO[0000] Error response from server, Error occurred while checking if volume volume_name exists: EOF
{
"Error": "Error response from server, Error occurred while checking if volume volume_name exists: EOF\n"
}
If I now change the volume name in my docker-compose from volume_name to e.g. volume_name_new, everything works fine.
Unfortunately I don't know what to do :(
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello everyone,
We had a power failure on our servers last night and since then I have noticed some strange behaviour on convoy.
A service could not be started and received the following error message:
create volume_name: Error occurred while checking if volume volume_name exists: EOF
So I tried to delete the volume, but got the following error:
If I now want to create a new volume manually, I get the following message:
If I now change the volume name in my docker-compose from volume_name to e.g. volume_name_new, everything works fine.
Unfortunately I don't know what to do :(
The text was updated successfully, but these errors were encountered: