Back in February 2020 Christian Boltz resigned from the openSUSE Board explaining the reasons behind his decision on the project mailing list. His resignation came about two weeks after Sarah Julia Kriesch's resignation from the Board.
The openSUSE Board was left with two vacant seats to be filled. Sarah had been a board member for just about a few weeks after the 2019-2020 board elections. After her resignation, the openSUSE Board decided to appoint Vinzenz Vietzke on the board based on the results of the 2019-2020 board elections. Following that, only one seat remained vacant on the board. However, before the Election Committee could start discussions for an election to fill that vacant seat, about two weeks after Vinzenz's appointment, openSUSE member Pierre Böckmann called for a No-Confidence vote against the current board. It was unprecedented in the community and that put things on halt for a while.
The board election rules state that:
If 20 per cent or more of the openSUSE members require a new board, an election will be held for the complete elected Board seats.
The Election Committee was tasked to find out whether 20% of the community is indeed calling for a re-election. At this point I should disclose that I am an election official in the openSUSE Election Committee and the task given to us was not easy. After much consultation, we finally came up with a way to "measure" this 20% requirement of the election rule. We set up an electronic petition using the voting platform that is used for openSUSE Board elections.
A few days ago the petition ended and the result showed that only 11.6% of the community was in favour of a re-election. That does not satisfy the requirement for a forced re-election and thus an ad-hoc election will be carried to fill the one vacant seat only.
Starting now and until the 2nd of August openSUSE members wishing to run for this election or nominate someone from the community can do so by sending an email to firstname.lastname@example.org. I wish to remind that only openSUSE members can run for board candidacy and vote in this election.
The Election Committee is composed of Ariez Vachha, Edwin Zakaria and myself.
Today, while pulling the latest Nextcloud container image from the docker.io repository I noticed that it is failing. Looking at the read: connection reset by peer error I assume it could be primarily due to network failure; maybe poor quality of the connection.
Note that Mauritius is far from "everywhere" else and connectivity issues are nothing new.
A few days ago there was a suggestion to implement a similar feature in Podman that is present in Buildah, which provides the image copy retry functionality.
For the curious, the implementation can be seen here.
Container images that are pulled by Buildah are stored in the local repository which can also by accessed by Podman, so that's an advantage. I tried pulling the Nextcloud container image using Buildah and it completed successfully.
Now, the downloaded container image is also accessible by Podman.
ish@coffee-bar:~> podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/libreoffice/online latest 0586fecfa3c1 28 hours ago 2.84 GB
docker.io/library/nextcloud latest 327476ebe328 3 days ago 774 MB
To conclude, while we are waiting that a retryCopyImage function is available in Podman, we can use Buildah to pull container images that are troublesome due to network issues.
Estu Fardani is a helpful & jovial fellow whom I met at the openSUSE Asia Summit last year in Bali, Indonesia. Recently, for the openSUSE Virtual Summit, Estu did a short presentation on Podman. His presentation video is available on YouTube and slides deck available on Google Slides.
While I am not a fan of alias docker=podman I believe Estu added that part in his slide below to make the Podman transition a bit smoother for users already familiar with Docker commands.
Note that the latest release of openSUSE Leap, i.e version 15.2, comes with support for Podman through the libcontainers-common package.
Previously, if one needed to experiment with Podman and/or deploy in production then openSUSE Tumbleweed, Kubic or MicroOS were the supported choices. Now, one may deploy Podman containers on their existing Leap infrastructure (after upgrading to the latest version 15.2).
२ जुलाई २०२० को openSUSE Leap 15.2 संस्करण उपलब्ध हुआ।
openSUSE Leap एक निशुल्क और लिनक्स-आधारित ऑपरेटिंग सिस्टम है जो आप अपने पीसी, लैपटॉप या सर्वर पर इस्तेमाल कर सकते है। Leap 15.2 और SUSE Linux Enterprise एक समान कोडबेस उपयोग करते है जिस से openSUSE Leap 15.2 की स्थिरता और ज्यादा मज़बूत होती है।
यह विशेष संस्करण कृत्रिम बुद्धिमत्ता, यानी आर्टिफिशियल इंटेलिजेंस, को अधिक आसानी से सुलभ बनाता है। निम्नलिखित पैकेज ऑफिशल रिपॉजिटरीज से प्राप्त किए जा सकते हैं।