|
Bugzilla – Full Text Bug Listing |
| Summary: | Docker fail to start on login | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User U7sZDHpPdJ <forgotten_U7sZDHpPdJ> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_U7sZDHpPdJ, igonzalezsosa, jreidinger, kanderssen, vrothberg |
| Version: | Leap 42.3 | Flags: | kanderssen:
needinfo?
(forgotten_U7sZDHpPdJ) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | systemctl status docker | ||
|
Description
Forgotten User U7sZDHpPdJ
2017-09-16 17:00:12 UTC
Created attachment 740821 [details]
systemctl status docker
It seems that by default on installation, openSUSE leap adds "suse" as domain name. When i removed it from yast -> Network settings, docker service is autostarted in login. So the issue is with the installer which adds a default suffix on hostname. Knut, please, could you have a look? knut ping With the current logs, I can't figure out what is happening, there are other docker issues reported with the same error messages and if the default hostname used by linurc is not valid (linuxrc sets it) then it is the first issue I get from it. https://github.com/openSUSE/linuxrc/blob/master/linuxrc_hostname.md So what is the expected fix? modify the default domain? I have just installed a Leap 42.3 and booted without update, installed docker, enabled docker and restarted. Docker starts fine and can't see anything relevant with journalctl. Could you please confirm that it still happens and attach the complete output of journalctl -u docker.service. Thn! I replaced my former btrfs installation with an ext4 one for performance reasons and I reinstall OpenSSL 42.3. Now it seems to be working as expected. I don,t know if there was something fixed in the meanwhile, but now it is working. (In reply to Diamantis Karagkiaouris from comment #8) > I replaced my former btrfs installation with an ext4 one for performance > reasons and I reinstall OpenSSL 42.3. Now it seems to be working as > expected. I don,t know if there was something fixed in the meanwhile, but > now it is working. Great, so, will consider it as invalid or fixed by now but be free to reopen it if you detect it is still failing in other installations you try. BTW thnx for reporting it ;) |