Skip to content

Commit ff0e41d

Browse files
committed
remote-session: use --net=host for remote cosa
It seems like podman purposely filters out local DNS resolvers like systemd-resolved in favour of directly mentioning specifying the upstream DNS servers. That messes up with a VPN setup we have though where we need to go through systemd-resolved to resolve hosts located on the VPN. Passing `--dns=127.0.0.53` would also work, but let's just simplify things further and pass through the host network. Ref: containers/podman#3277
1 parent 13583cc commit ff0e41d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

cmd/remote-session.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ func preRunCheckEnv(c *cobra.Command, args []string) error {
135135
// COREOS_ASSEMBLER_REMOTE_SESSION environment variable.
136136
func runCreate(c *cobra.Command, args []string) error {
137137
podmanargs := []string{"--remote", "run", "--rm", "-d",
138-
"--pull=always", "--privileged", "--security-opt=label=disable",
138+
"--pull=always", "--net=host", "--privileged", "--security-opt=label=disable",
139139
"--volume", remoteSessionOpts.CreateWorkdir,
140140
"--workdir", remoteSessionOpts.CreateWorkdir,
141141
// Mount required volume for buildextend-secex, it will be empty on

0 commit comments

Comments
 (0)