github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-24 00:56:55 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

The network of the action container run by runner is inconsistent, which makes it impossible to access the git address in the intranet. #14929

New Issue
Closed
opened 2025-11-02 11:26:03 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 11:26:03 -06:00
Owner
Copy Link

Originally created by @imblowsnow on GitHub (Sep 6, 2025).

Description

Environment

  • gitea container
    • name = gitea-server
    • network = gitea
  • runner container
    • name = gitea-runner
    • network = gitea

GITEA_INSTANCE_URL = http://gitea-server:3000/

Gitea and the runner are in the same Docker network and are connected properly.

When the runner runs, a network is automatically generated.

GITEA-ACTIONS-TASK-3_WORKFLOW-Gitea-Actions-Demo_JOB-Explore-Gitea-Actions-Explore-Gitea-Actions-network

This is not in the current gitea container's network.

fatal: unable to access 'http://gitea-server:3000/blowsnow/easytier-client/': Could not resolve host: gitea-server

Gitea Version

1.24.2

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

None

Originally created by @imblowsnow on GitHub (Sep 6, 2025). ### Description # Environment - gitea container - name = gitea-server - network = gitea - runner container - name = gitea-runner - network = gitea GITEA_INSTANCE_URL = http://gitea-server:3000/ Gitea and the runner are in the same Docker network and are connected properly. When the runner runs, a network is automatically generated. GITEA-ACTIONS-TASK-3_WORKFLOW-Gitea-Actions-Demo_JOB-Explore-Gitea-Actions-Explore-Gitea-Actions-network This is not in the current gitea container's network. fatal: unable to access 'http://gitea-server:3000/blowsnow/easytier-client/': Could not resolve host: gitea-server ### Gitea Version 1.24.2 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? docker ### Database None
GiteaMirror added the type/bug label 2025-11-02 11:26:03 -06:00
GiteaMirror commented 2025-11-02 11:26:04 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Sep 6, 2025):

1640e9a490/custom/conf/app.example.ini (L72-L77)

@wxiaoguang commented on GitHub (Sep 6, 2025): https://github.com/go-gitea/gitea/blob/1640e9a490f61c3abf7fb842eae7d0a0ed6314ce/custom/conf/app.example.ini#L72-L77
GiteaMirror commented 2025-11-02 11:26:04 -06:00
Author
Owner
Copy Link

@imblowsnow commented on GitHub (Sep 6, 2025):

gitea/custom/conf/app.example.ini

Lines 72 to 77 in 1640e9a

;; Controls how to detect the public URL.
;; Although it defaults to "legacy" (to avoid breaking existing users), most instances should use the "auto" behavior,
;; especially when the Gitea instance needs to be accessed in a container network.
;; * legacy: detect the public URL from "Host" header if "X-Forwarded-Proto" header exists, otherwise use "ROOT_URL".
;; * auto: always use "Host" header, and also use "X-Forwarded-Proto" header if it exists. If no "Host" header, use "ROOT_URL".
;PUBLIC_URL_DETECTION = legacy

This should be useless. It's not in a network.

fatal: unable to access 'http://gitea-server:3000/blowsnow/easytier-client/': Could not resolve host: gitea-server

Why can't I specify the network of the container?

@imblowsnow commented on GitHub (Sep 6, 2025): > [gitea/custom/conf/app.example.ini](https://github.com/go-gitea/gitea/blob/1640e9a490f61c3abf7fb842eae7d0a0ed6314ce/custom/conf/app.example.ini#L72-L77) > > Lines 72 to 77 in [1640e9a](/go-gitea/gitea/commit/1640e9a490f61c3abf7fb842eae7d0a0ed6314ce) > > ;; Controls how to detect the public URL. > ;; Although it defaults to "legacy" (to avoid breaking existing users), most instances should use the "auto" behavior, > ;; especially when the Gitea instance needs to be accessed in a container network. > ;; * legacy: detect the public URL from "Host" header if "X-Forwarded-Proto" header exists, otherwise use "ROOT_URL". > ;; * auto: always use "Host" header, and also use "X-Forwarded-Proto" header if it exists. If no "Host" header, use "ROOT_URL". > ;PUBLIC_URL_DETECTION = legacy This should be useless. It's not in a network. fatal: unable to access 'http://gitea-server:3000/blowsnow/easytier-client/': Could not resolve host: gitea-server Why can't I specify the network of the container?
GiteaMirror commented 2025-11-02 11:26:04 -06:00
Author
Owner
Copy Link

@TheFox0x7 commented on GitHub (Sep 6, 2025):

You can?
https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L72

@TheFox0x7 commented on GitHub (Sep 6, 2025): You can? https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L72
GiteaMirror commented 2025-11-02 11:26:04 -06:00
Author
Owner
Copy Link

@imblowsnow commented on GitHub (Sep 6, 2025):

You can? https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L72

thanks, it is normal

@imblowsnow commented on GitHub (Sep 6, 2025): > You can? https://gitea.com/gitea/act_runner/src/branch/main/internal/pkg/config/config.example.yaml#L72 thanks, it is normal
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14929
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?