01:00 <Matthieu[m]1> did you use the coreos-installer tool?

01:00 <Matthieu[m]1> it is not clear in your explanations

06:45 <bgilbert> baaash[m]: could you post a console log?

08:00 <dngray[m]> <dngray[m]> "is it my imagination or docker-..." <- hmm i just might make a `Makefile` to build my containers

08:00 <dngray[m]> wonder if fcos has `make`

08:00 <dngray[m]> seeing as docker-compose like depends on python, and all that nonsense

08:01 <bgilbert> dngray[m]: it does not have make

08:01 <dngray[m]> hmm.

08:01 <dngray[m]> well i guess it has bash 😁

08:02 <dngray[m]> maybe i can do something with that buildah thing instead

08:09 <dngray[m]> they were supposed to be integrating "compose" into "docker" at some point

08:10 <dngray[m]> https://docs.docker.com/compose/reference/

08:10 <dngray[m]> that should make a lot of fcos users happy cos they won't need the python tool then

08:16 <dngray[m]> i guess another way i might do this is just have an arch vm, where i build the stuff, and use fcos to run it

12:26 <anthr76[m]> dngray[m]: is it possible for you to use systemd with podman to manage your containers?

12:27 <dngray[m]> yeah that's what i'm thinking of doing

12:27 <dngray[m]> build the images elsewhere, and run them with systemd

14:33 <dustymabe> ravanelli: is anyone using https://github.com/coreos/coreos-assembler/blob/main/src/cosalib/manifest.py right now?

14:33 <dustymabe> that you know of

14:38 <ravanelli> dustymabe: no, I don't think so

20:38 <dustymabe> saqali: since you opened the original FCOS tracker issue: https://github.com/coreos/fedora-coreos-config/pull/1870

22:22 <baaash[m]> <matthieu[m]> "did you use the coreos-installer..." <- thanks for your reply... initially, no... it wasn't clear to me what methodology I should use... in my haste to get something working I've tried several different methods. I think my issue was with SELinux labelling. I'm taking a step back and trying to read up as much of the docs as possible to gain more clarity.

22:22 <baaash[m]> This is all fairly new to me.

23:04 <Matthieu[m]1> well, I guess your VM has network connection to the virtual network interface (something like 192.168.122.0/24), which means your VM cannot access to 192.168.1.1 directly.

23:04 <Matthieu[m]1> As a side effect, perhaps your apache server (on the host) is listening on the virtual network interface, meaning you could reach it from your coreos VM.

23:04 <Matthieu[m]1> During the setup of the network, you can add route to be able to route 192.168.1.0/24 addresses from your VM. here is the doc https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-configuring_static_routes_using_nmcli

23:04 <Matthieu[m]1> I would recommand you set up the network inside the Fedora CoreOS livesystem (after booting the ISO file), then you can use the coreos-installer tool with the option --copy-network.

23:21 <baaash[m]> > <@matthieu[m]:libera.chat> well, I guess your VM has network connection to the virtual network interface (something like 192.168.122.0/24), which means your VM cannot access to 192.168.1.1 directly.... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/6932940dcddf0134b1fef88d9644d05564dc549c)

23:27 <Matthieu[m]1> ah yes if you use the podman0 bridge, so you get access to the container itself

23:27 <Matthieu[m]1> anyway you cannot use the adress 192.168.1.1, it is not routable like this

23:29 <baaash[m]> spoke too soon.. too tired... I introduced a change and hadn't re-sourced my bashrc. sorry for the noise folks

23:31 <baaash[m]> > <@matthieu[m]:libera.chat> ah yes if you use the podman0 bridge, so you get access to the container itself

23:31 <baaash[m]> >

23:31 <baaash[m]> > anyway you cannot use the adress 192.168.1.1, it is not routable like this

23:31 <baaash[m]> ok thanks matthieu. I'm making progress again now.

23:44 <Matthieu[m]1> :)