heldwin has quit [Remote host closed the connection]
paragan has joined #fedora-coreos
bytehackr has joined #fedora-coreos
Arkanterian has joined #fedora-coreos
jcajka has joined #fedora-coreos
heldwin has joined #fedora-coreos
bytehackr has quit [Remote host closed the connection]
Betal has quit [Quit: WeeChat 3.6]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 265 seconds]
<guesswhat>
Question, are Podman runtime requirements already included in FCOS min hw requirements? ( 2vCPU, 4G Ram )? I am running "custom scheduler" in container which is using podman socket and wondering if should I assing custom cpuset to podman and then to this "custom scheduler" and left rest for containers and OS itself. Thanks
crobinso has joined #fedora-coreos
jpn has joined #fedora-coreos
Arkanterian has quit [Quit: Client closed]
jbrooks has quit [Read error: Connection reset by peer]
jbrooks has joined #fedora-coreos
fifofonix has joined #fedora-coreos
vgoyal has joined #fedora-coreos
<dustymabe>
podman is just a container runtime. the overhead should be low - after that it's just processes on a linux system
<dustymabe>
I'd say just group the podman resources in "OS resources"
<dustymabe>
and wall those "OS resources" off from the application(s)
nalind has joined #fedora-coreos
mheon has joined #fedora-coreos
plarsen has joined #fedora-coreos
<dustymabe>
👋 jbrooks - meeting in a few minutes, right?
<mnguyen_>
dustymabe, let me know when you have the ibmcloud account setup for me
ScottEdlund[m] has joined #fedora-coreos
crobinso has quit [Ping timeout: 250 seconds]
<dustymabe>
mnguyen_: you should get an invite
<guesswhat>
any idea why podman system df takes long time ( 18s vs 0,5s in docker )
<guesswhat>
this is warn message from podman service `Sep 29 14:41:05 ip-10-2-2-30 podman[6324]: time="2022-09-29T14:41:05Z" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"`
<jlebon>
guesswhat: might be a better question for #podman
<mnguyen_>
dustymabe: yes i've just been in meetings
<dustymabe>
+1
crobinso has joined #fedora-coreos
<dustymabe>
jlebon: I need a hand hold.. The PR that merged earlier today against the releng automation repo triggered a new container build for `coreos-ostree-importer` in OpenShift and it's not happy. Could use a screenshare session to brainstorm debugging ideas.
Arkanterian has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
c4rt0 has joined #fedora-coreos
c4rt0 has quit [Remote host closed the connection]
<jlebon>
dustymabe: free now. can do now or after lunch
cyberpear has quit [Quit: Connection closed for inactivity]
Arkanterian has quit [Quit: Client closed]
Betal has joined #fedora-coreos
<fifofonix>
fedora-coreos-docs question. seems a nginx.conf is expected by the preview.sh script in the root directory? is there a sample for that?
<ravanelli>
dustymabe: ppc64le baremetal install works for FCOS37. 🎉
<ravanelli>
I will try to get an aarch64 for now in Beaker for it
<dustymabe>
ravanelli: good to know. Thank you for testing
<mnguyen_>
`BMCOSUI090200: You do not have the required permission to create an instance. You must be assigned the IAM Editor role or higher. Contact the account owner to update your access.` on ibmcloud :-(
<dustymabe>
in a separate commit
<fifofonix>
dustymabe: check
<dustymabe>
mnguyen_: let me look
<dustymabe>
mnguyen_: what specific steps are you running?
<mnguyen_>
creating the bucket for the fcos image i believe
<mnguyen_>
`ibmcloud resource service-instance-create "${BUCKET}-service-instance" cloud-object-storage standard global
<mnguyen_>
`
<davdunc[m>
dustymabe: The website work for Cloud Edition was the revamp that mizo and ekidney are working on.