linka-cloud / linka-cloud/d2vm
docker networking with default gateway issue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 373
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
the command is not working if a network with a default gateway is used. for my build of other containers i fixed this by adding "--network host" on the build command. Is there any way to tell d2vm to add "--network host" to the build command ?
the issue i get is "W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Connection timed out [IP: 151.101.2.132 80]" im using the container to build it. it's wokring on my local system but not on my cloud build server, since the build server has only an internal network and adds a route default route/gateway for internet downloads.
basically i should be able to solve it by adding "--network host" to the build command, is there any way give additional parameters for the used build command ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the d2vm entry point that invokes the container build command and review how Dockerfile builds are configured. Check whether additional build parameters can be forwarded, then verify that supplying --network host allows the Debian download to complete on an internally networked build server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100