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

Can't config network #34

Closed
fancl20 opened this issue Jul 26, 2019 · 6 comments
Closed

Can't config network #34

fancl20 opened this issue Jul 26, 2019 · 6 comments

Comments

@fancl20
Copy link

fancl20 commented Jul 26, 2019

fcct removed the networkd section from ct. Also, the network extension is not a valid systemd unit extension.

So what's the correct way to config the network now?

@ajeddeloh
Copy link
Contributor

Fedora CoreOS uses NetworkManager, not networkd. Configuring the network should be done by writing config files for networkmanager. We may want to add sugar for that later though.

@J0WI
Copy link

J0WI commented Oct 14, 2019

Can you provide some docs and examples to help with the migration?

@ashcrow
Copy link
Member

ashcrow commented Oct 14, 2019

cc'ing @bgilbert @dustymabe to see if they have some already

@kallisti5
Copy link

I was looking at testing this... so there's no network or hostname configuration in fcct?

@f35f0ef9d0e827dae86552d3899f78fc
Copy link

f35f0ef9d0e827dae86552d3899f78fc commented Mar 12, 2020

Here's how you configure hostname:

storage:
  files:
    - path: /etc/hostname
      mode: 420
      overwrite: true
      contents:
        inline: |
          hostname.domain.local

EDIT: This is related to #60

@bgilbert
Copy link
Contributor

The hostname can be configured as in #34 (comment), and other NetworkManager configuration can be written as in these docs.

Closing this out.

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

No branches or pull requests

7 participants