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

Feedback: Week 8 CoreOS #11

Open
shekhargulati opened this issue Feb 22, 2016 · 3 comments
Open

Feedback: Week 8 CoreOS #11

shekhargulati opened this issue Feb 22, 2016 · 3 comments
Labels

Comments

@shekhargulati
Copy link
Owner

Please provide your feedback by posting a comment against this issue.

@brianredbeard
Copy link

CoreOS isn't built on ChromeOS. They both use the same SDK, but technically Gentoo is the upstream. CoreOS maintains their own eBuilds and keeps a portage mirror on GitHub.

@shekhargulati
Copy link
Owner Author

thanks @brianredbeard I will make the changes.

@llarsson
Copy link

That journalctl command you write in the end only happens to work by lucky accident. Had fleet scheduled the unit onto another machine, you would not be able to access it via journalctl, which only works on the local host.

fleetctl journal -f hello.service would work, regardless of where the unit has been scheduled.

The divide between what is operating locally (systemd and journalctl), and what fleet does to unify them into a cluster-wide system is probably one of the more conceptually difficult topics in CoreOS.

You might also need to mention that SSH agent forwarding (with your key added) is really useful, since that is required for many of the fleetctl commands that need to access other hosts (such as pulling info from the journal, or actually logging in to them for you via SSH, to go to where the unit is running).

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

3 participants