Does Octopus Deploy Tentacle for Linux support Red Hat Enterprise Linux (RHEL) 6? I've tried installing and it doesn't work.
The short answer is no.
Our documentation states that Tentacle for Linux is distributed as self-contained .NET core application. Self-contained applications do not rely on shared-components being present on the target system, all of the necessary components for the application to run are included within the application itself.
Red Hat Enterprise Linux 6 (RHEL 6) required the Runtime Identifier (RID) rhel-x64 RID whereas linux-x64 is compatible with most distributions like CentOS, Debian, Fedora, Ubuntu and RHEL 7+. Rather than support two versions of Tentacle for Linux, the decision was made to use the linux-x64 RID.
Here is a list of Linux distributions that are supported.
Related
The docs say stuff like "Windows x64", but what does it mean with regards to operating system versions? What Windows Server is it compatible with, for example?
Same thing with "Linux x64", there is no such operating system of course, it all comes down to a particular minimal kernel version requirement, perhaps a minimum glibc version or something.
Is this information available anywhere please?
Windows builds are supported on Windows 7 and 10, and on Windows Server 2008, 2012, and 2016.
Says by official docs on GitHub
I am trying to use the tensorflow-GPU serving in the windows 10 system. But I haven't found any solution for installing the Nvidia docker for windows. Please give me a suggestion, how to use the Windows machine GPU in deployment.
Neither of nvidia-docker and nvidia-container-runtime have support for Windows, and there are no plans so far to support the OS either. Only linux host is supported.
Check the FAQ here:
Is macOS supported?
No, we do not support macOS (regardless of the version), however you
can use the native macOS Docker client to deploy your containers
remotely (refer to the dockerd documentation).
Is Microsoft Windows supported?
No, we do not support Microsoft Windows (regardless of the version),
however you can use the native Microsoft Windows Docker client to
deploy your containers remotely (refer to the dockerd
documentation).
I have a task to update 8.5.5.2 web sphere to 8.5.5.14 on a windows 2008 server. I have java 1.7 already installed (and java 6 as well) and all the profiles uses it.
How ever when i try to apply fix patch using IBM installation manager, by default it's installing Java 8 which is not supported on windows 2008.
Is there a way where i can by pass java 8 and install only the fix patch (8.5.5.14) from installation manager.
Any pointer/help would be really appreciated. Thanks.
Installation Manager Screenshot:
No, WebSphere 8.5.5.14 requires Java 8, and Java 8 is not supported on Windows 2008 Server. If you must stay with Windows 2008 you can't update WebSphere past 8.5.5.13. More detail here: IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems
This is what IBM documentation ( https://www-01.ibm.com/support/docview.wss?uid=swg27045339 ) says, I did some shortcuts to make key points easier to notice in a long article:
In 8.5.5.14 and later, it is planned that (Java8) SDK will be required for all new installations and all updates (fixpacks).
In 8.5.5.14 (...) prior operating system releases (such as Windows 2008 (...) ) will no longer be supported.
So unfortunately what you are trying to do is not supported:
Although Java7 is still fine as a runtime environment for your servers, for example if your business application is not yet Java8 compatible, you need to have Java8 installed as a default JVM for Websphere 8.5.5.14 "internal" requirements.
You cant have IBM's Java8 installed in Windows2008, which is mandatory for Websphere 8.5.5.14, that means you cant install Websphere 8.5.5.14.
In the end, I would like to remind you, that you can upgrade to a previous release: 8.5.5.13. Version 8.5.5.13 is 11 fixpacks newer than what you already have, maybe it will suffice for your needs.
Bottom line - upgrade windows to a current version that's not 11 years old. Or, better yet, put it on Linux. WAS is great on Linux! Red Hat, Suse, OpenSuse, Fedora, CentOS are good flavors.
Hello im new on this type of software i had serch on Google about MQ but all what i find is that it can be install on linux windows xp ...
so this may be stupid but is there any way to install MQ on windows server
is there any way to install MQ on windows server
Yes. If you have purchased it you should be able to download it for production use via IBM Passport Advantage, all the details can be seen here:
https://www-01.ibm.com/support/docview.wss?uid=swg24043697
If you only want to use it for personal developer use, you can use the free developer edition, which can be found here:
https://developer.ibm.com/messaging/mq-downloads/
So for clarity, 9.1 is the latest LTS (long term service) release, 9.1.1 is the latest CD (continuous delivery) release. Which is more useful depends on what you are trying to use. It is supported on a range of operating systems, including Windows.
From the 9.1 SOE (System requirements), this is supported in windows server 2016 and windows server 2012r2 (that's the server o/s's as well Windows 10 and 8.1 for desktops). If you need older operating system support, you need to look at older MQ releases, such as 9.0*, 8.0* etc.
MQ windows drivers can be installed on any windows machine, depending upon the system requirement for particular MQ, it is not restricted to Windows XP only
System Requirements for MQ 9.1
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=B560B760819A11E6B5854315721876AE&osPlatforms=Windows
System Requirements for MQ 9.0
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=8360DD50895F11E5816C133BBD3A3812&osPlatforms=Windows
System Requirements for MQ 8.0
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Windows
Has anybody tried and succeeded with installing flutter on win x86?
(no VM of course)
My question is not about what Google SAYs, but why do YOU think it is possible or not possible. I do not see anything in the source at github that may prevent it from running on win x86 apart that google does not want to provide support for x86, because it is not a priority.
If you think it is not possible, can you please provide some idea why before saying No or voting down
====BACKGROUND====
prerequisites for the flutter sdk on windows are:
dart 2.0
PowerShell 5.0 or newer
Git for Windows
inside there are also some java and libcurl executables
all of the above exist in win x86 versions
plus the rest seems to be just dart source code.
I run flutter on Ubuntu.
I have an older laptop with win 7 x86 pro which I do not want to upgrade to x64
I tried to use x64 win installation
replacing dart 2.0 x64->x86
and then using flutter doctor to update.
(flutter uses dart pub with "update" function changed to "upgrade", but this can be fixed)
the update using flutter doctor in fact runs just to the point of updating flutter_tool
then trying to update some flutter_tool related packages it comes up with an ERROR:
cannot resolve the library URL
The Windows installation page says:
To install and run Flutter, your development environment must meet
these minimum requirements:
Operating Systems: Windows 7 SP1 or later (64-bit)
And there is a recent comment (20 Aug 2018) from one of the Flutter developers that also states:
We don't have any plans to support 32-bit Windows. That said, if
anyone is willing to send pull requests to get Flutter running on
32-bit Windows, we'd gladly review the PRs.
A further response from the Flutter devs outlines some of the reasons why this is the case:
Someone would need to author 32-bit build rules in the
engine/buildroot repos to build a 32-bit SDK -- specifically the
Dart VM and gen_snapshot. Ideally, the rules would also emit the
target architecture Android artifacts as well.
The design of gen_snapshot (our AOT compiler) assumes identical host
and target architecture bitness. Only a 64-bit build of gen_snapshot
can output arm64 target binaries. Fixing this would involve a
significant amount of work.