-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker daemon gets started on nodes #243
Milestone
Comments
Right, we should disable it with a MachineConfig |
IMO docker should be disabled by preset in FCOS (in all of Fedora even!). |
Thank you for reporting this @dustymabe! |
Any reason to have Docker installed at all? I know it comes by default with FCOS, but why would OKD need it installed by default. |
@Fodoj OKD uses FCOS' rpm-ostree composes and we don't currently plan on doing an OKD-specific compose. |
binnes
added a commit
to binnes/okd
that referenced
this issue
Jul 11, 2023
* Add docker/podman instructions for site update and fix broken links after switch to MkDocs site (okd-project#238) (okd-project#2) * move from master to main branch * remove blog entry re creating blog on old site * Add site README * add CNAME in docs so gets published * Delete CNAME * fix CNAME for production site Signed-off-by: Brian Innes <[email protected]> * fixed links re MkDocs going live + container tooling instructions Signed-off-by: Brian Innes <[email protected]> * added Windows support for docker based tooling Signed-off-by: Brian Innes <[email protected]> * added podman instructions Signed-off-by: Brian Innes <[email protected]> * tidy up commands Signed-off-by: Brian Innes <[email protected]> Co-authored-by: Brian Innes <[email protected]> Co-authored-by: Brian Innes <[email protected]> * added primary working group information Signed-off-by: Brian Innes <[email protected]> Co-authored-by: Brian Innes <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In FCOS we include the moby-engine package to provide the docker CLI/daemon for users who want that. In OKD I don't think we want the service to start at all as we run containers with
cri-o
(or in some very few casespodman
). Right now the docker service is socket activated and I think something within kubernetes/openshift is hitting that socket and starting the daemon.Should we mask the service for now? It would save us the 150+ MiB hit:
Versions
openshift-install-linux-4.5.0-0.okd-2020-06-29-110348-beta6
32.20200629.2.0
The text was updated successfully, but these errors were encountered: