Skip to content

upgrade container based documentation build environment.#862

Merged
SteveMacenski merged 1 commit intoros-navigation:masterfrom
fujitatomoya:upgrade-container-build-env
Feb 9, 2026
Merged

upgrade container based documentation build environment.#862
SteveMacenski merged 1 commit intoros-navigation:masterfrom
fujitatomoya:upgrade-container-build-env

Conversation

@fujitatomoya
Copy link
Copy Markdown
Contributor


Basic Info

Info Please fill out this column
Ticket(s) this addresses (N/A)
Does this PR contain AI-generated software? (No)

Description of contribution in a few bullet points

This PR fixes the container based documentation build environment.

Signed-off-by: Tomoya.Fujita <tomoya.fujita825@gmail.com>
Comment thread .devcontainer/devcontainer.json
Comment thread Dockerfile
Comment thread Dockerfile
Comment thread Makefile
Copy link
Copy Markdown
Member

@SteveMacenski SteveMacenski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll be honest that I don't use devcontainers nor plan to, so these are contributions from other users.

bind all NICs available in this host.

these scripts do not really things instead of giving the permission to git. but now nav2doc is created and bound to the working directory /doc, so this is not needed anymore. for the maintainability, i would suggest to remove them from here.

Do you think either of these changes would be controversial for any devcontainer users? If not, happy to merge. This seems sensible to me though (but I didn't test if the user removes the need for setting the directory as safe -- but I assume you did).

@fujitatomoya
Copy link
Copy Markdown
Contributor Author

I'll be honest that I don't use devcontainers nor plan to, so these are contributions from other users.

no worries. i do use devcontainer most likely, so i just came up with this PR to enable it. if you do not like this, we can just drop it. but if you take it, i can make sure that works without problems. (if you have issues, just sign me up 👍)

Do you think either of these changes would be controversial for any devcontainer users?

--host 0.0.0.0 is a standard and pretty much expected setup for doc development, so i do not think this is controversial. but the scripts on-create-command.sh‎ is required to stay unless we take the fix for devcontainer in this PR. i believe current configuration of devcontainer has the security issue, because it starts the container with root permission. user could accidentally delete files without any warning.

@SteveMacenski SteveMacenski merged commit d165e01 into ros-navigation:master Feb 9, 2026
10 checks passed
@SteveMacenski
Copy link
Copy Markdown
Member

Sounds good!

mach0312 pushed a commit to mach0312/docs.nav2.org that referenced this pull request Feb 12, 2026
…ion#862)

Signed-off-by: Tomoya.Fujita <tomoya.fujita825@gmail.com>
Signed-off-by: Jaerak Son <sjr9017@naver.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants