[Bug 1168139] New: /home partition on container not writable
http://bugzilla.suse.com/show_bug.cgi?id=1168139 Bug ID: 1168139 Summary: /home partition on container not writable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner@suse.de Reporter: petr.vorel@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 834299 --> http://bugzilla.suse.com/attachment.cgi?id=834299&action=edit Travis LTP build log Tumbleweed container (opensuse/tumbleweed) cannot write into /home (or there is some other I/O error or other error): ls: cannot access '.': Operation not permitted configure: error: working directory cannot be determined I found that in LTP travis job https://travis-ci.org/github/linux-test-project/ltp/jobs/668710329 It looks like it started 3 days ago (27 March) https://travis-ci.org/github/linux-test-project/ltp/builds Leap container is working well. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168139 http://bugzilla.suse.com/show_bug.cgi?id=1168139#c1 --- Comment #1 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Petr Vorel from comment #0)
Created attachment 834299 [details] Travis LTP build log
Tumbleweed container (opensuse/tumbleweed) cannot write into /home (or there is some other I/O error or other error):
ls: cannot access '.': Operation not permitted configure: error: working directory cannot be determined
I found that in LTP travis job https://travis-ci.org/github/linux-test-project/ltp/jobs/668710329
It looks like it started 3 days ago (27 March) https://travis-ci.org/github/linux-test-project/ltp/builds
Leap container is working well.
Travis uses an too old Ubuntu version ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168139 http://bugzilla.suse.com/show_bug.cgi?id=1168139#c2 --- Comment #2 from Petr Vorel <petr.vorel@suse.com> --- (In reply to Thorsten Kukuk from comment #1)
Leap container is working well.
Travis uses an too old Ubuntu version ...
Thanks for info. Does it mean, that nobody in Travis is not able to use Tumbleweed container? What caused that incompatibility? (it was working 4 days ago). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168139 http://bugzilla.suse.com/show_bug.cgi?id=1168139#c3 Petr Vorel <petr.vorel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Petr Vorel <petr.vorel@suse.com> --- I got hint from Michael Vetter on IRC, I'll implement it. Suppose it's Travis issue, so closing now. https://github.com/profanity-im/profanity/issues/1294 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168139 http://bugzilla.suse.com/show_bug.cgi?id=1168139#c4 Michael Vetter <mvetter@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvetter@suse.com --- Comment #4 from Michael Vetter <mvetter@suse.com> --- I had this just a couple of days ago. Please see https://github.com/profanity-im/profanity/issues/1294 We solved this by using a newer docker version in Travis. See https://docs.travis-ci.com/user/docker/#installing-a-newer-docker-version Example: https://github.com/wstrm/profanity/commit/bec7189295b5eb0cf47d06575f563c94c9... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com