-
Notifications
You must be signed in to change notification settings - Fork 496
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
Container is not able to connect to the internet using the bridge network on Synology DSM 7.2 #552
Comments
today i followed the docker-support network tutorials with alpine. setting them up and running them internet access is possible, dns works and pinging servers and other containers poses no problems. is there a configuration problem in the redmine image when uses with synology dsm? |
Can you post any logs showing what you're talking about? No ping is not installed inside the container. You can install it if you like. There is no networking setup required when making a docker image, its all just handled by either docker or the base image. I know one other user had issues with 5.1+ and synologies older kernel. #549 |
Hi and thanks for your fast response. Martin :) |
I've got plenty on my plate so no need to rush |
Hi Jonathan, Any suggestions as how to migrate the data in the most secure way. Of course i will read the available information on your site. with best regards martin |
Hmm, I'm glad you got a fresh server up and running. In general, the migration between versions should go smoothly. The only issues I've ever run into were with 3rd party plugins which have always made it difficult for me to upgrade redmine versions. With that in mind, I always recommend making a test copy of the container and volumes to test the migration on, in case things go wrong, you can then delete the test copy and reach out for help. If your still having trouble migrating your older database, logs would be mandatory to have any hope of figuring out what is going on. Also set DEBUG=true in the docker environment. |
Hi Jonathan, as redmine installation and testing is done in my spare time (being a gynecologist and obstetrician in a german hospital near hamburg) i´ll just accept this and start afresh with the new working configuration. with best regards martin ps: |
For the log files you can volume mount the log directory so you can view them outside of the docker. I'm not sure what a simple filesystem repo is. Could you link to the redmine wiki page? Note i am on vacation though the next week so dont have a computer handy. I will help as i can. |
I tried to install the latest redmine image (5.1.2) after using redmine up to version 4.2.1 since a few years. I found that the actual image is not able to load ruby from the server which seems to be included up to version 5.1.0 of the image. At least 5.1.0 is the last version, which runs on my Synology ds920 (system and packages most recent versions). Also email is not available. So the bridge network seems not to be able to connect to the internet.
I set up a rule in the firewall to enable all ports for the bridge network IPs (172.18.0.0/16). But to no avail.
So: Sameersbn/redmine runs well up to version 5.1.0. Starting from 5.1.1 it doesn ´t boot up as the container cannot load ruby from th servers. It seems that the bridge network is blocked by Synology dsm, so that it is not able to get to the internet. Access to the redmine website is perfectly possible via the configured ports or via reverse proxy on my ds.
I tried to several versions of the image and defined version 5.1.1 onward as the ones where the problems started. The only difference in the container settings where that before 5.1 ruby 2.5 was included whereas starting from 5.1. ruby 3.2 is downloaded from a server.
Even before push emails and notifications could not be sent by the container. (So the principal problem existed from the beginning, it just wasn ´t so visible as I didn’t need notifications then.)
i introduced a rule in the firewall which allowed all ports for the bridge-networks ip addresses. I hoped that that would grant access to the internet for the container. Nothing happened.
I switched to the host network. There redmine booted up to version 5.1.2 but I was not able to get access to the container (defined port 30001 as redmine port and outgoing port of the container.
So there seems to be something fundamentally flawed in the networking settings either on the side of the container or Synology ´s.
An help? The ping-command seems not to be available in the container´s terminal. Is that true?
The text was updated successfully, but these errors were encountered: