I tried to install podman on SLES 12 straightforwardly, but it looks like the package is missing.
dmitry#sles12:~> sudo zypper in podman
Refreshing service 'Advanced_Systems_Management_Module_x86_64'.
Refreshing service 'Containers_Module_x86_64'.
Refreshing service 'Legacy_Module_x86_64'.
Refreshing service 'Public_Cloud_Module_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Server_x86_64'.
Refreshing service 'Web_and_Scripting_Module_x86_64'.
Loading repository data...
Reading installed packages...
'podman' not found in package names. Trying capabilities.
No provider of 'podman' found.
Resolving package dependencies...
Nothing to do.
The only piece of information I found about running podman on SLES 12 is
SLES 12 is a bad platform to play with current container technology.
It's too old for that and build/based around docker, not podman.
source: https://lists.opensuse.org/opensuse-kubic/2019-10/msg00009.html
As far as I know SLES 12 is still supported.
I checked the latest release notes of SLES 12 SP4 and SLES 12 SP5, these two were released after the first public release of podman, but there is no any mention of podman.
Podman is not officially provided for SLE-11.
Please have a look at the release notes of SLES 15 SP2 ("5.2.1 Support for podman"):
Starting with SUSE Linux Enterprise Server 15 SP2, podman is a supported container engine. However, certain features of podman are currently not supported: [...]
Source: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/#jsc-SLE-9112
You could try an unsupported version of podman by using the package from the community-based Virtualization:containers repository:
https://build.opensuse.org/package/show/Virtualization%3Acontainers/podman
Exemplary procedure:
zypper ar --refresh https://download.opensuse.org/repositories/Virtualization:/containers/SLE_12_SP5/Virtualization:containers.repo
zypper ref
zypper in podman
You'd surely need to accept/trust the repo's signing details during the procedure and eventually you're going to need to install additional dependencies from other repositories as well.
Moving to SLES 15 SP2 might be the easier way to go.
Related
I managed to compile QEMU (3.0.50) under Windows 10 (64-bit) (basically following these instructions) with these commands:
./configure --enable-gtk --enable-sdl
make
However, when starting qemu-system-x86_64.exe in a console, nothing happens. I expected a window showing up. Shortly after starting the exe, I'm getting back the prompt. Nothing printed out to the console. No necessary DLL is missing. What could be the problem?
Finally I managed to compile and run QEMU under Windows 10 Home 64-bit.
There are a few pitfalls:
Due to a compiler bug in mingw (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86832 and https://www.mail-archive.com/qemu-devel#nongnu.org/msg557409.html), you have to configure QEMU with --disable-stack-protector and (one solution) add the function __stack_chk_fail to a source file.
Configure QEMU with --disable-werror.
Remove Capstone project from makefile.
Here's a complete step-by-step guide for compiling qemu-system-x86_64.exe:
Date: 2018-10-31
OS: Microsoft Windows 10 Home 64-bit
Guide based on: https://wiki.qemu.org/Hosts/W32#Native_builds_with_MSYS2
Download and install msys2 to C:\msys64:
http://repo.msys2.org/distrib/x86_64/msys2-x86_64-20180531.exe
Start C:\msys64\mingw64.exe
Updates (then close window and restart mingw64.exe): pacman -Syu
Updates: pacman -Su
Install basic packets: pacman -S base-devel mingw-w64-x86_64-toolchain git python
Install QEMU specific packets: pacman -S mingw-w64-x86_64-glib2 mingw-w64-x86_64-gtk3 mingw-w64-x86_64-SDL2
Get QEMU sources:
git clone git://git.qemu-project.org/qemu.git
cd qemu
git submodule update --init ui/keycodemapdb
git submodule update --init capstone
git submodule update --init dtc
Insert
void __stack_chk_fail(void);
void __stack_chk_fail(void)
{
}
to qemu\util\oslib-win32.c
e.g. at line 44
Comment out (#) Capstone (line 508) in qemu\Makefile
Build QEMU:
./configure --enable-gtk --enable-sdl --target-list=x86_64-softmmu --disable-werror --disable-stack-protector
make
Run in qemu/x86_64-softmmu
./qemu-system-x86_64 -L ./../pc-bios
Optional (for better performance): Install HAXM according to this guide: https://www.qemu.org/2017/11/22/haxm-usage-windows/ and start QEMU with option -accel hax
I would do know if somebody tried in 2022 i have currently some issues after compiling.
Firt it asks for libzstd.dll, when i go to the project i found by google and dl this dll, i encounter another issue
with x64.dll
with x32.dll (just in case)
i use msys2 minGw x64 on windows 10 pro x64. At the beginning i would compile a patch, but it the same problem with vanilla, i ask myself if it's an environment problem, a missing dll, or if it's always possible to compile directly on windows10, perhaps now it's only possible to compile in cross platform. I'm not habit at all with mingw64 tools.
I looked for the g_spanw... error and found this https://docs.gtk.org/glib/func.spawn_async_with_fds.html
Perhaps i'm wrong but it's only for gnome, isn't it ?
I am attempting to install closed source software from Silego, GreenPAK Designer, on a machine running Fedora 19. The supported installation packages on Silego's Website only target Ubuntu and Debian. I downloaded the .deb package and used Alien to convert to an RPM. So far so good, but a dry run of yum install showed dependency errors, which I solved by installing the necessary packages with yum:
qt5-qbase
qt5-qbase-gui
qt5-qtdeclarative
qt5-qtlocation
qwt
Now, yum installed the above libraries in /usr/lib/ but the GreenPAK RPM defaults to /usr/local/bin as the output dir. I figured I could run
sudo yum localinstall --nodeps --noscripts greenpak-designer-x.x.x.rpm
and get a successful install but I received conflict errors relating to dirs such as '/', '/usr', '/usr/bin' etc. I worked around this issue with:
rpmrebuild -pe --notest-install --replacefiles --noscripts greenpak-designer.x.x.x.rpm
and removing the offending lines in the script. It allowed me to install rpm but the software is broken because of dependency issues (not surprisingly). From the system log:
Jan 4 16:06:49 pelican gnome-session[1729]: /usr/local/greenpak-designer/bin/GP5: error while loading shared libraries: libicui18n.so.52: cannot open shared object file: No such file or directory
The machine has a /usr/lib/libicui18n.so.50
One thing I did not try is rebuilding my shared object cache with ldconfig, which sometimes solves problems with missing .so links when building from source but I don't see how that would apply in this instance (I'm not trying to link object files to libraries, rather simply trying to drop binaries in default install locations, no?)
Of course, I contacted the vendor and begged for an RPM. The contact was helpful but informed me the software folks are on a well deserved break. I thought I'd continue puttering with this in the meantime while I have time.
Any ideas? It seems the solution to this problem would be helpful when trying to install almost any closed source software targeting Debian on a Fedora box.
I just installed a fresh copy of Fedora 24 Workstation and did a full dnf update on the entire system.
Then I installed the jProfiler rpm from the jProfiler site.
However, when I try to launch jProfiler (either from the /opt/jprofiler9/jProfiler.desktop icon or from /opt/jprofiler9/bin/jprofiler shell script), I get the following error message:
java.awt.HeadlessException
at java.awt.SplashScreen.getSplashScreen(SplashScreen.java:117)
at com.exe4j.runtime.splash.AwtSplashScreen.<init>(AwtSplashScreen.java:17)
at com.exe4j.runtime.splash.SplashEngine.setJavaSplashScreenConfig(SplashEngine.java:17)
at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:50)
I've tried setting my display using DISPLAY=0.0 or even DISPLAY=:0, but neither seem to make any difference/impact.
Any suggestions how to get this to work? I suspect it is something obvious that I am overlooking.
After a bunch of trial and error, I finally tried to install the Oracle Hotspot JRE instead of the OpenJDK JRE. I downloaded Oracle's JDK, installed it, and then configured it as the system default using:
sudo alternatives --config java
Now everything works properly with Oracle JRE.
On my Fedora 19 system, yum update attempts to reinstall a large number packages I have previously removed. This should not happen, as the packages listed are not installed and should not be suggested by yum. How can I make yum work in the expected manner - with updates suggesting only upgrades to preinstalled packages.
Background: I have been trying out new DEs - installing and removing them as I go. Currently, I'm in a DE-less state, booting directly into a tty terminal. My system has no (or a few hidden) xfce or cinnamon packages to "upgrade", yet the package manager is suggesting 300 packages to install, totaling 600M of new install.
Terminal output gist:
https://gist.github.com/Redoubts/29400f0b98cd13120a6a#file-gistfile1-txt
Short answer - It's not possible to disallow installing any packages from the depenency chain. Either you install all of them or drop those who depends on unwanted packages.
In some cases, when the package from a dependency chain is required only during some specific stages of installation (say for execution of a pre- or post-install scripts), it's possible to remove thise package later, after the complete installation. But that's not what you want I suppose.
I've installed Google Chrome on Hardy via the .deb file and would like to configure apt-get for automatic updates.
[I have another machine running Ubuntu Karmic where this works fine; apt-get knows the package as 'google-chrome'; I'm now using a Dell Mini 10 with Ubuntu 8.04 LTS installed]
As part of the .deb install, two entries have been added to the third- party software sources tab:
http://dl.google.com/linux/deb stable main
http://dl.google.com/linux/deb stable non-free main
However if I check for updates with either of these clicked, I get the following error:
Failed to fetch http://dl.google.com/linux/deb/dists/stable/Release Unable to find expected entry main/binary-lpia/Packages in Meta-index file (malformed Release file?)
There is a thread here which indicates others have had the same problem:
http://www.google.co.uk/support/forum/p/Chrome/thread?tid=097d103f87b49abe&hl=en
This references a further thread:
http://code.google.com/p/chromium/issues/detail?id=38608
which suggests the problem has been fixed.
Despite this I remain unable to get it to work, and none of the suggested workarounds seem to work either.
Ideas ? Thanks.
I think the issue here is that the Ubuntu installaion on your Dell Mini uses LPIA (Low Power Intel Architecture) and the Google Software Repository doesn't provide the "google-chrome" package for this architecture. Hence apt-get is giving you an error. You will have to do the updates manually using the "google-chrome" package for the i386 architecture.
On another note, the following thread provides details about repackaging an i386 package for LPIA. I hope this helps.
http://ubuntuforums.org/showthread.php?t=962835