Skip to content
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

Podman container support #1811

Open
q2dg opened this issue Aug 14, 2020 · 11 comments
Open

Podman container support #1811

q2dg opened this issue Aug 14, 2020 · 11 comments
Labels
Milestone

Comments

@q2dg
Copy link

q2dg commented Aug 14, 2020

Hello. Have you considered Podman container support? Its API is very similar to Docker's one.
I would be great for running Gns3 in RedHat/Fedora/CentOS hosts, where Docker isn't officially available.
Furthermore, it increases the security of all.
Thanks!

@grossmj grossmj added this to the 3.1 milestone Aug 15, 2020
@grossmj grossmj modified the milestones: 3.1, TBD Oct 22, 2021
@elico
Copy link

elico commented Mar 3, 2022

@grossmj @q2dg any progress with this?
I wouldn't worry about security with Docker, the whole rootless point is good but up to the point when you really trust the product and the code.
Docker is pretty mature to be trusted enough for GNS3.
The main issue is compatibility on:
RHEL 8+
Fedora 33+
CentOS 8+
Oracle Enterprise Linux 8+
....

Which I use all the above.

@q2dg
Copy link
Author

q2dg commented Oct 16, 2022

Yes, after more than two years without any official response, this compatibility issue starts to be a blocking one,

@rb83
Copy link

rb83 commented Jan 6, 2023

It almost works.

But at the moment podman will always create network interfaces in the container, even when requested not to do so. This prevents ubridge from moving interfaces to the container's namespace & renaming them, since they already exist with the same name inside the container. This is a podman issue, not a GNS3 issue.

With regards to security, it's completely independent of wether one uses Docker or Podman, as GNS3 currently requires the containers to be rootfull anyway (also see #1944).

@benyaminl
Copy link

benyaminl commented Jan 13, 2023

does this include podman.socket needed?

Does this normal when we see this problem on the container for starting?

image

@rb83
Copy link

rb83 commented Jan 13, 2023

@benyaminl that error message is misleading (the GNS3 GUI thinks the container's stdout error message is related, but it's not). The process fails earlier, as described in my previous message.

You have to use docker for the time being.

@benyaminl
Copy link

@rb83 So sad :')

Thanks for clear things up.. Probably I will use full Qemu VM for now. Thank you!

@grossmj grossmj modified the milestones: TBD, 3.1, 3.2 Jan 30, 2023
@q2dg
Copy link
Author

q2dg commented Jul 31, 2023

Well, it seems bad Podman's behaviour, which was a no-go in this issue until resolved, is finally resolved: containers/podman#16716

@benyaminl
Copy link

@q2dg have you test it on newest GNS3? Does it work?

@grossmj grossmj modified the milestones: 3.2, 3.1 Aug 1, 2023
@q2dg
Copy link
Author

q2dg commented Aug 1, 2023

Not yet. I'll update this thread with new information when I get it

@RushingAlien
Copy link

Still same /etc/hosts issue looks like

@q2dg
Copy link
Author

q2dg commented Nov 28, 2023

I'm waiting to new Podman's v.5.0, where there are some changes in its internal network stack. When released I'll give feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants