moving ipa2 to a second subnet

[danlavu]

• making this environment more realistic
• moved the network create to use the docker command because docker-compose defaults the isolation value to true

[danlavu]

This should work, @justin-stephenson, can you please test this? Something may be foo bar on my workstation, but I think it should work. The second network is created and master.ipa2.test is provisioned correctly. The problem is that 'sssd' network is not routable to the 'ipa' network.

However, both the 'sssd' and 'IPA' networks are routable from the host and the ad vagrant network.

[justin-stephenson]

This should work, @justin-stephenson, can you please test this? Something may be foo bar on my workstation, but I think it should work. The second network is created and master.ipa2.test is provisioned correctly. The problem is that 'sssd' network is not routable to the 'ipa' network.

However, both the 'sssd' and 'IPA' networks are routable from the host and the ad vagrant network.

Hi,

I built this PR but cannot ping master.ipa2.test or 172.16.110.10 from master.ipa.test , I see some errors about dns in the journal.

May 05 15:26:10 fedora.test.local dns[856731]: dnsmasq[60]: query[A] master.ipa2.test from 172.16.100.1
May 05 15:26:15 fedora.test.local aardvark-dns[856608]: 5346 dns request got empty response

Sorry I can't help much here I don't have much experience with networking

[danlavu]

Thanks for testing, it's not my workstation, @jakub-vavra-cz suggested something that I will look into.

[danlavu]

@thalman solved it. docker-compose and podman-compose creates networks differently. Docker creates the network with isolation = true while podman has it set to false. Added another commit, changing docker-compose.

[danlavu]

After talking to @thalman and seeing the ci failures. podman-compose isn't installed on other distros. I'm going to create the networks using the docker command and have docker-compose use pre-existing networks, so there is no dependency on podman-compose.

[danlavu]

@pbrezina yea, it's done, just needs testing. Moving it out of draft.

[thalman]

LGTM

[danlavu]

Okay, being unfamiliar with the Makefile there were a number of mistakes. I figured them out, there are enough changes from Tomas's review that it should be reviewed again. The containers are now being built successfully.

• added make start (doesn't create the networks), in the event you just wanted to start the containers from being stopped.
• The compose function has a condition for up|down to execute the script

[justin-stephenson]

@danlavu I tried to make build locally and it fails because I don't have docker running, but I can't install docker due to dependency failure it seems.

+ docker-compose -f ../docker-compose.yml -f ./docker-compose.build.yml up --detach
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
>>>> Executing external compose provider "/usr/libexec/docker/cli-plugins/docker-compose". Please see podman-compose(1) for how to disable this message. <<<<

unable to get image 'localhost/sssd/ci-base-ipa:latest': Cannot connect to the Docker daemon at unix:///run/user/1000/podman/podman.sock. Is the docker daemon running?
Error: executing /usr/libexec/docker/cli-plugins/docker-compose -f ../docker-compose.yml -f ./docker-compose.build.yml up --detach: exit status 1
+ cleanup
make: *** [Makefile:3: build] Error 1
justin@justin-fedora:~/github/sssd-ci-containers$ sudo dnf install docker
[sudo] password for justin: 
Sorry, try again.
[sudo] password for justin: 
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
Problem: problem with installed package
  - installed package podman-docker-5:5.6.2-1.fc42.noarch conflicts with docker provided by moby-engine-27.5.1-1.fc42.x86_64 from fedora
  - installed package podman-docker-5:5.6.2-1.fc42.noarch conflicts with moby-engine provided by moby-engine-27.5.1-1.fc42.x86_64 from fedora
  - package podman-docker-5:5.6.2-1.fc42.noarch from updates conflicts with docker provided by moby-engine-27.5.1-1.fc42.x86_64 from fedora
  - package podman-docker-5:5.6.2-1.fc42.noarch from updates conflicts with moby-engine provided by moby-engine-27.5.1-1.fc42.x86_64 from fedora
  - package podman-docker-5:5.4.1-1.fc42.noarch from fedora conflicts with docker provided by moby-engine-27.5.1-1.fc42.x86_64 from fedora
  - package podman-docker-5:5.4.1-1.fc42.noarch from fedora conflicts with moby-engine provided by moby-engine-27.5.1-1.fc42.x86_64 from fedora
  - conflicting requests
  - installed package podman-docker-5:5.6.2-1.fc42.noarch conflicts with docker provided by moby-engine-28.5.1-2.fc42.x86_64 from updates
  - installed package podman-docker-5:5.6.2-1.fc42.noarch conflicts with moby-engine provided by moby-engine-28.5.1-2.fc42.x86_64 from updates
  - package podman-docker-5:5.6.2-1.fc42.noarch from updates conflicts with docker provided by moby-engine-28.5.1-2.fc42.x86_64 from updates
  - package podman-docker-5:5.6.2-1.fc42.noarch from updates conflicts with moby-engine provided by moby-engine-28.5.1-2.fc42.x86_64 from updates
  - package podman-docker-5:5.4.1-1.fc42.noarch from fedora conflicts with docker provided by moby-engine-28.5.1-2.fc42.x86_64 from updates
  - package podman-docker-5:5.4.1-1.fc42.noarch from fedora conflicts with moby-engine provided by moby-engine-28.5.1-2.fc42.x86_64 from updates
You can try to add to command line:
  --allowerasing to allow removing of installed packages to resolve problems
  --skip-broken to skip uninstallable packages

[justin-stephenson]

By the way @pbrezina may want to look and review this PR.