I installed Sentry on premise last friday and everything was fine.
I have tried to do it again since yesterday but I am losing the host ping after installation
Environment : Centos 7, docker 20.10.2 and docker-compose 1.27.4
I launch the installation and the host ping at the same time. The ping response is ok
The first time (last thursday), I tried to install Sentry and yes, there was not enough space on the disk but the message from the installation was clear (no space left…) and it failed. So, I added 30 G
The host has 10G Mem Free, I hope that’s enough.
Like I said, the installation succed on friday last week, the host and Sentry was available. But now, I lost the connection with the host as soon as the command line “creating network “sentry_onpremise_default” with the defalut driver” is executed during the installation.
I noticed that there was more informations between friday and monday (Applying sentry.0…), a deployment this weekend?
Everytime you install Sentry, docker-compose deletes and then creates a new internal network. It binds the Nginx container to the host’s port 9000 so this shouldn’t really matter. That said if you are sure this is the issue, I’d check my firewall (iptables?) settings, especially around Docker and internal networks.
I forgot to tell you something important. I install Sentry on a virtual machine.
I took a snapshot of my VM with only docker and docker-compose just before installing Sentry and if I start docker without Sentry, I don’t lose the ping.
And, I restore the snapshot before I start an installation of Sentry.