Hi!
This post is a guide to install “ABAP Platform Developer Edition 1909” from a VMWare virtual machine and using the LINUX SUSE distribution.
System
Sudo zypper install docker. And we can start the service with: sudo systemctl start docker.service. If we also want Docker to start when starting the virtual machine, we can execute: sudo systemctl enable docker.service. As you can see, we have everything ready to install our S4Hana developer edition. Downloading the Docker image. Linux Shout published a tutorial about installing AlmaLinux 8 image in Docker Container. How to install AlmaLinux 8 Image in Docker Container. Download and run AlmaLinux 8 on Docker Container by pulling its latest image from Docker Hub on any Cloud server, Linux, Windows, or macOS.
- To install the docker and docker-compose packages start YaST2, select 'Software' and start the module 'Software Management'. Search for docker and choose to install the Packages 'docker' and 'python3-docker-compose'. (Even though the package is called 'python3-docker-compose', it installs 'docker-compose' binary).
- Installing using Docker¶ Docker is awesome, it allows users to run w3af without installing any of it’s dependencies. The only pre-requisite is to install docker, which is widely supported. Once the docker installation is running these steps will yield a running w3af console.
- 4 CPUs
- 16GB RAM
- 150GB Disk
Tools
- VMWare: https://www.vmware.com/es/products/workstation-player.html
- Docker Hub account: https://www.docker.com/
- SUSE image: https://www.suse.com/es-es/download/ in my case, https://software.opensuse.org/distributions/leap?locale=es
We access the VMWare program and go to the option “Create a new virtual machine”
We select the Linux image that we have downloaded, in my case SUSE
Add name to the virtual machine (free choice)
150 GB of free disk is recommended for installation, so we can 160BG to give something to the operating system
In the next step, click on the “Customize Hardware” option to modify the specifications of the machine, these will be the parameters:
Finally we press “Finish” to start the installation.
Installing SUSE
Once the configuration is finished, the SUSE installation will start automatically, the first screen that will appear we will press “Installation”:
We accept the license and configure the keyboard language:
When pressing “Next” it will ask us if we want to additionally install YaST2, we will mark “yes”:
The next step is the configuration of online repositories, in this we will mark the following options and click on next:
When the next step appears we select the option: “Desktop with GNOME”
We are pressing “Next” until the following screen appears
Click on “Guided Setup”, and add these settings:
- In the first screen we do not select anything, only “Next”
- In “File System Type” we select “Ext4” and “Next”
After pressing Next we will return to the “Suggested partitions” screen and we will press Next, we configure the location:
Next step configure our user, we add our name, the user name that we want, and a password:
In the step “Installation Settings” we have to look at these options:
Click “Install” to start the installation, again we need some patience to finish the installation:
Setup Linux
We are going to configure the IP to have a fixed reference. To do this, we go to network settings:
Click on options in the active connection:
We add the manual method in the IPv4 option, adding this data, or similar ones according to your local network configuration. This will allow us to always use the same IP. Make sure that this IP is not assigned to another device connected to your router
We are going to configure the localhost files, for this we execute the following commands:
Where we add the name: vhcala4hci and press Ctrl + O to save and Ctrl + X to exit the editor.
And this second command:
We will add the following entry:
With the IP that we have configured by default and press Ctrl + O to save and Ctrl + X to exit the editor.
Install Docker Ce On Suse Linux
To install Docker it is as easy as running the following commands:
And we can start the service with:
If we also want Docker to start when starting the virtual machine, we can execute:
As you can see, we have everything ready to install our S4Hana developer edition
Downloading the Docker image
The first thing is to login to the docker server, this is because the image that we are going to use is not available in public mode, but we can only download it in private mode at € 0.0.
We can proceed with the download with the command:
Once finished we will see the following message:
Before starting the container, we will add some extra configurations, executing:
Once finished we execute the following command to start the container on the host vhcala4hci, we will also use the -p parameter to allow access to the indicated ports from outside the virtual machine:
We will see how the services are activated. Finally we will see this message indicating that we can now use our new SAP.
These are the data, remember that the IP will depend on the configuration made according to your IP:
And we can now access. The user to access is: DEVELOPER with password Ldtf5432
Enjoy it!
Install Docker On Sles 12 Sp4
Table of Contents
- Alternate installation methods
- Certbot-Auto
Certbot is meant to be run directly on a web server, normally by a system administrator. In most cases, running Certbot on your personal computer is not a useful option. The instructions below relate to installing and running Certbot on a server.
System administrators can use Certbot directly to request certificates; they should not allow unprivileged users to run arbitrary Certbot commands as root, because Certbot allows its user to specify arbitrary file locations and run arbitrary scripts.
Certbot is packaged for many common operating systems and web servers. Check whethercertbot (or letsencrypt) is packaged for your web server’s OS by visitingcertbot.eff.org, where you will also find the correct installation instructions foryour system.
Note
Unless you have very specific requirements, we kindly suggest that you use the installation instructions for your system found at certbot.eff.org.
Certbot currently requires Python 2.7 or 3.6+ running on a UNIX-like operatingsystem. By default, it requires root access in order to write to/etc/letsencrypt, /var/log/letsencrypt, /var/lib/letsencrypt; tobind to port 80 (if you use the standalone plugin) and to read andmodify webserver configurations (if you use the apache or nginxplugins). If none of these apply to you, it is theoretically possible to runwithout root privileges, but for most users who want to avoid running an ACMEclient as root, either letsencrypt-nosudo or simp_le are more appropriate choices.
The Apache plugin currently requires an OS with augeas version 1.0; currently itsupportsmodern OSes based on Debian, Ubuntu, Fedora, SUSE, Gentoo and Darwin.
If you are offline or your operating system doesn’t provide a package, you can usean alternate method for installing certbot.
Most modern Linux distributions (basically any that use systemd) can installCertbot packaged as a snap. Snaps are available for x86_64, ARMv7 and ARMv8architectures. The Certbot snap provides an easy way to ensure you have thelatest version of Certbot with features like automated certificate renewalpreconfigured.
You can find instructions for installing the Certbot snap athttps://certbot.eff.org/instructions by selecting your server software and thenchoosing “snapd” in the “System” dropdown menu. (You should select “snapd”regardless of your operating system, as our instructions are the same acrossall systems.)
Docker is an amazingly simple and quick way to obtain acertificate. However, this mode of operation is unable to installcertificates or configure your webserver, because our installerplugins cannot reach your webserver from inside the Docker container.
Most users should use the instructions at certbot.eff.org. You should only useDocker if you are sure you know what you are doing and have a good reason to doso.
You should definitely read the Where are my certificates? section, in order toknow how to manage the certsmanually. Our ciphersuites pageprovides some information about recommended ciphersuites. If none ofthese make much sense to you, you should definitely use the installation methodrecommended for your system at certbot.eff.org, which enables you to useinstaller plugins that cover both of those hard topics.
If you’re still not convinced and have decided to use this method, fromthe server that the domain you’re requesting a certficate for resolvesto, install Docker, then issue a command like the one found below. Ifyou are using Certbot with the Standalone plugin, you will needto make the port it uses accessible from outside of the container byincluding something like -p80:80 or -p443:443 on the commandline before certbot/certbot.
Running Certbot with the certonly command will obtain a certificate and place it in the directory/etc/letsencrypt/live on your system. Because Certonly cannot install the certificate fromwithin Docker, you must install the certificate manually according to the procedurerecommended by the provider of your webserver.
There are also Docker images for each of Certbot’s DNS plugins availableat https://hub.docker.com/u/certbot which automate doing domainvalidation over DNS for popular providers. To use one, just replacecertbot/certbot in the command above with the name of the image youwant to use. For example, to use Certbot’s plugin for Amazon Route 53,you’d use certbot/dns-route53. You may also need to add flags toCertbot and/or mount additional directories to provide access to yourDNS API credentials as specified in the DNS plugin documentation.
For more information about the layoutof the /etc/letsencrypt directory, see Where are my certificates?.
Warning
While the Certbot team tries to keep the Certbot packages offeredby various operating systems working in the most basic sense, due todistribution policies and/or the limited resources of distributionmaintainers, Certbot OS packages often have problems that other distributionmechanisms do not. The packages are often old resulting in a lack of bugfixes and features and a worse TLS configuration than is generated by newerversions of Certbot. They also may not configure certificate renewal for youor have all of Certbot’s plugins available. For reasons like these, werecommend most users follow the instructions athttps://certbot.eff.org/instructions and OS packages are only documentedhere as an alternative.
Arch Linux
Debian
If you run Debian Buster or Debian testing/Sid, you can easily install certbotpackages through commands like:
If you run Debian Stretch, we recommend you use the packages in Debianbackports repository. First you’ll have to follow the instructions athttps://backports.debian.org/Instructions/ to enable the Stretch backports repo,if you have not already done so. Then run:
In all of these cases, there also packages available to help Certbot integratewith Apache, nginx, or various DNS services. If you are using Apache or nginx,we strongly recommend that you install the python-certbot-apache orpython-certbot-nginx package so that Certbot can fully automate HTTPSconfiguration for your server. A full list of these packages can be foundthrough a command like:
They can be installed by running the same installation command above butreplacing certbot with the name of the desired package.
Ubuntu
If you run Ubuntu, certbot can be installed using:
Optionally to install the Certbot Apache plugin, you can use:
Fedora
FreeBSD
- Port:
cd/usr/ports/security/py-certbot&&makeinstallclean - Package:
pkginstallpy27-certbot
Gentoo
The official Certbot client is available in Gentoo Portage. From theofficial Certbot plugins, three of them are also available in Portage.They need to be installed separately if you require their functionality.
Note
The app-crypt/certbot-dns-nsone package has a differentmaintainer than the other packages and can lag behind in version.
NetBSD
- Build from source:
cd/usr/pkgsrc/security/py-certbot&&makeinstallclean - Install pre-compiled package:
pkg_addpy27-certbot
OpenBSD
- Port:
cd/usr/ports/security/letsencrypt/client&&makeinstallclean - Package:
pkg_addletsencrypt
Other Operating Systems
OS packaging is an ongoing effort. If you’d like to packageCertbot for your distribution of choice please have alook at the Packaging Guide.
We used to have a shell script named certbot-auto to help people installCertbot on UNIX operating systems, however, this script is no longer supported.If you want to uninstall certbot-auto, you can follow our instructionshere.
When using certbot-auto on a low memory system such as VPS with less than512MB of RAM, the required dependencies of Certbot may fail to build. This canbe identified if the pip outputs contains something like internalcompilererror:Killed(programcc1). You can workaround this restriction by creatinga temporary swapfile:
Disable and remove the swapfile once the virtual environment is constructed:
Installation from source is only supported for developers and thewhole process is described in the Developer Guide.
Warning
Please do not use pythoncertbot/setup.pyinstall, pythonpipinstallcertbot, or easy_installcertbot. Please do not attempt theinstallation commands as superuser/root and/or without virtual environment,e.g. sudopythoncertbot/setup.pyinstall, sudopipinstall, sudo./venv/bin/.... These modes of operation might corrupt your operatingsystem and are not supported by the Certbot team!