Replies: 1 comment 1 reply
-
Sorry, my fail. It's solved. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
our developers needs a single rabbit instance for Testing stuff.
So I've build ip a debian 10 and run Rabbit (Version 3.6.6-alpine-manage) with the follow command:
Everything runs fine for much months.
Then the docker container log grows up and run in to out of disk space.
Because the rabbit work path is outside of the container my idea was to stop and prune the current container and restart it with the command below:
The docker image is exact the same like the first start but now rabbit crash a few minutes after the start.
Here the log:
I would have expected rabbit to continue working with the given data.
Instead rabbit tries to update and change the data after startup.
Does rabbit do something different in the official Docker image on the first startup compared to each subsequent startup of the same container?
If yes, what?
And is it possible to disable this in my case?
Regards,
HF
Beta Was this translation helpful? Give feedback.
All reactions