-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
How to add new network interface , such as ethX to runc instance? #83
Comments
i think the filesystem when the runc mounts will be a read only filesystem through rootfs and in returns dont create any pid files or saves any data in the necessary locations .I have this read-only issue when i was trying to check on some of the running resources packaged inside the container image |
oh sorry if i'm wrong but the reffered issue gives me a light on this to try within the mounted container
|
@cloudtrends Now I think you can only create interface connected to host and then move it to your container namespace :/ Libcontainer has basic veth pair support though. |
You can see my response here for how to setup networking for containers spawned by runc Thanks! |
hi all,
I am using a centos base image to running runc instance .
After enter into the runc instance , I could found the default generated network interface file:
/etc/sysconfig/network-scripts/ifcfg-ens3
After config the above file , what confused me is that : there is no support such as :
none above files exists in the runc instance .
Why I need the network interface is because that I want run a network service in runc , such as :
python -m SimpleHTTPServer 8000
And above service can visited from outside of runc environment .
Can I archive this with runc ?
The text was updated successfully, but these errors were encountered: