Skip to content

Conversation

@Pratiksha0102
Copy link

No description provided.

@Pratiksha0102 Pratiksha0102 requested a review from djkabutar May 14, 2025 04:42
@djkabutar
Copy link
Member

Is this required, just making all required configs as module in kernel will suffice that, this is not required then.

@Pratiksha0102
Copy link
Author

Docker doesn't work with configs as a module.

@djkabutar
Copy link
Member

If we are always going to build the kernel with the docker fragmented config then there is no meaning of doing this way, rather giving all the configs in the rockchip_linux_defconfig makes more sense. The fragment is needed when sometime those configs needs to enabled for some device and for some device those are not required.

@Pratiksha0102
Copy link
Author

Yes, this is for that purpose. We can disable this fragment if we don't want to include Docker in the kernel image. It's meant to keep the Docker configuration separate. In the future, when we release this build publicly, users will be able to identify the Docker-related configurations and disable them if they don't need Docker within kernel.

@djkabutar
Copy link
Member

I don't think requiring a separate kernel build for the docker is necessary, it can be embedded into the rockchip_linux_defconfig only

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