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

FileNotFoundError: [Errno 2] No such file or directory: '/run/containers/registries.conf' #23

Open
miabbott opened this issue Sep 15, 2017 · 7 comments

Comments

@miabbott
Copy link

On the Fedora Atomic Host Continuous stream[0], the registries service is failing to start:

# systemctl status registries
● registries.service - SystemWide Container Registries
   Loaded: loaded (/usr/lib/systemd/system/registries.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2017-09-15 17:13:47 UTC; 4min 1s ago
  Process: 706 ExecStart=/usr/libexec/registries -o /run/containers/registries.conf -V REGISTRIES (code=exited, status=1/FAILURE)
 Main PID: 706 (code=exited, status=1/FAILURE)
      CPU: 584ms

Sep 15 17:13:47 fedora26ah-dev registries[706]:     do_output(output, args)
Sep 15 17:13:47 fedora26ah-dev registries[706]:   File "/usr/lib/python3.6/site-packages/registries/registries.py", line 50, in do_output
Sep 15 17:13:47 fedora26ah-dev registries[706]:     write_file(args.output, output)
Sep 15 17:13:47 fedora26ah-dev registries[706]:   File "/usr/lib/python3.6/site-packages/registries/registries.py", line 34, in write_file
Sep 15 17:13:47 fedora26ah-dev registries[706]:     with open(filename,"w") as f:
Sep 15 17:13:47 fedora26ah-dev registries[706]: FileNotFoundError: [Errno 2] No such file or directory: '/run/containers/registries.conf'
Sep 15 17:13:47 fedora26ah-dev systemd[1]: registries.service: Main process exited, code=exited, status=1/FAILURE
Sep 15 17:13:47 fedora26ah-dev systemd[1]: Failed to start SystemWide Container Registries.
Sep 15 17:13:47 fedora26ah-dev systemd[1]: registries.service: Unit entered failed state.
Sep 15 17:13:47 fedora26ah-dev systemd[1]: registries.service: Failed with result 'exit-code'.

# journalctl -b -u registries
-- Logs begin at Thu 2017-08-31 14:16:30 UTC, end at Fri 2017-09-15 17:16:10 UTC. --
Sep 15 17:13:45 fedora26ah-dev systemd[1]: Starting SystemWide Container Registries...
Sep 15 17:13:47 fedora26ah-dev registries.log_warning[706]: /etc/containers/registries.conf is in YAML format and should be in TOML format. Back this file up and then use /usr/libexec/registries_migrator > /etc/
Sep 15 17:13:47 fedora26ah-dev registries[706]: Traceback (most recent call last):
Sep 15 17:13:47 fedora26ah-dev registries[706]:   File "/usr/libexec/registries", line 11, in <module>
Sep 15 17:13:47 fedora26ah-dev registries[706]:     load_entry_point('registries==0.1', 'console_scripts', 'registries')()
Sep 15 17:13:47 fedora26ah-dev registries[706]:   File "/usr/lib/python3.6/site-packages/registries/registries.py", line 146, in registries
Sep 15 17:13:47 fedora26ah-dev registries[706]:     do_output(output, args)
Sep 15 17:13:47 fedora26ah-dev registries[706]:   File "/usr/lib/python3.6/site-packages/registries/registries.py", line 50, in do_output
Sep 15 17:13:47 fedora26ah-dev registries[706]:     write_file(args.output, output)
Sep 15 17:13:47 fedora26ah-dev registries[706]:   File "/usr/lib/python3.6/site-packages/registries/registries.py", line 34, in write_file
Sep 15 17:13:47 fedora26ah-dev registries[706]:     with open(filename,"w") as f:
Sep 15 17:13:47 fedora26ah-dev registries[706]: FileNotFoundError: [Errno 2] No such file or directory: '/run/containers/registries.conf'
Sep 15 17:13:47 fedora26ah-dev systemd[1]: registries.service: Main process exited, code=exited, status=1/FAILURE
Sep 15 17:13:47 fedora26ah-dev systemd[1]: Failed to start SystemWide Container Registries.
Sep 15 17:13:47 fedora26ah-dev systemd[1]: registries.service: Unit entered failed state.
Sep 15 17:13:47 fedora26ah-dev systemd[1]: registries.service: Failed with result 'exit-code'.

This happened when the atomic.spec file changed here:

http://pkgs.fedoraproject.org/cgit/rpms/atomic.git/commit/?id=336bf59b64dc212d36b41d5dd577fde13d6f56ee

...and then atomic-registries was built from git master.

[0] https://pagure.io/fedora-atomic-host-continuous

@mikkeljohnsen
Copy link

mikkeljohnsen commented Dec 6, 2017

This is a serious bug. It stopped all our dockers from running.

SOLUTION: Downgrade to 1.19.1-5.git48c224b.el7 on (CentOS and SL)

@baude
Copy link
Member

baude commented Dec 6, 2017

@mikkeljohnsen are you still seeing this and on what OS?

@mikkeljohnsen
Copy link

mikkeljohnsen commented Dec 6, 2017

@baude I'm on Scientific Linux.

This will fail to start: atomic-registries-1.20.1-3.git840732d.el7.x86_64

But atomic-registries-1.19.1-5.git48c224b.el7.x86_64 works

I found similar problems on CentOS (on google)

@mikkeljohnsen
Copy link

mikkeljohnsen commented Dec 6, 2017

But looking at the error, I'm not 100% it was the same.

The file "/usr/libexec/registries" is completely different in 1.20.1 and the error was on line 5.

Something about "Module" (from pkg_resources import load_entry_point)

@baude
Copy link
Member

baude commented Dec 6, 2017

@mikkeljohnsen there is a new version of registries with a couple of changes. Are you on freenode by chance? I'm rangerpb there...maybe we can talk there and hash this out ?

@miabbott
Copy link
Author

miabbott commented Dec 6, 2017

Something about "Module" (from pkg_resources import load_entry_point)

That sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1520466

@baude
Copy link
Member

baude commented Dec 6, 2017

just need python-setuptools for that one.

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

3 participants