According to the documentation the Galera Manager can be installed on Ubuntu or AWS L2.
Incidentally, at this point, Galera Manager runs either Ubuntu or Amazon Linux 2. Future releases of Galera Manager may allow for other distributions of Linux.
This doesn't appear to be the case though, as the installer start by complaining about
WARN[0000] Debian / Ubuntu / Linux / focal / 20.04
and then asks a few questions before croaking with;
ERRO[0347] unsupported host os
I have tried 16.04, 18.04 and 20.04 without success. I haven't boot up an AWS instance as I don't want to run the GM in the cloud. Any thoughts/observations welcome.
Related
I want to deploy a python project to ubuntu instance on aws from a windows operating system, but all tutorials I have encountered either use ubuntu or mac as their development/local machine.
Is the deployment from windows the same i.e. after createing the instance all I would then be doing from the local windows system would be running inside the ubuntu instance?
is there any tutorial which can help me achieve my objective?
Note i am deploying directly without git.
ANy help would be appreciated
To transfer files to an ubuntu instance you could use SSH, from windows you could download an SSH client such as Mobaxterm (https://mobaxterm.mobatek.net/)! or download Windows Subsystem for Linux (https://learn.microsoft.com/en-us/windows/wsl/install-win10)! then use SCP to copy files (https://www.computerhope.com/unix/scp.htm)!. Both options require that you have the .pem security file for your instance
Your best bet is going to be installing WSL(Windows Subsystem for Linux) and using that to run bash commands. This will make your life a whole lot easier as you won't have to look for Windows specific tutorials and you can now follow Ubuntu/Linux tutorials.
What is WSL? It is essentially a Linux VM built into Windows. It will provide you with a terminal running Ubuntu or pretty much any other Linux distro you could want.
How to install WSL
According to GCP's OS patch management, patch jobs can be created for the Compute Instance VMs that have the OS config agent installed in them.
This document explains how to install the agent if it is not there already in some VMs.
Operating systems it covers are:
Windows Server / Ubuntu / Debian / RHEL / CentOS SLES / openSUSE
How to create a patch job for compute instances with Google container optimized os (COS)?
I am not able to find a way to install the OS config agent in these COS instances neither an option to create a "OS Patch Deployment". Is this even possible?
Unfortunately, you're not able to use OS patch management for VM instances with Google Container Optimized OS.
Please have a look at the documentation Creating patch jobs section Supported operating systems:
Debian 9
Ubuntu 16.04 and 18.04
CentOS 6, 7, and 8
Red Hat Enterprise Linux (RHEL) 6, 7, and 8
Windows Server 2012R2, 2016, 2019, and semi-annual releases 1803 and 1809
SUSE Enterprise Linux Server (SLES) 12 and 15, openSUSE Leap 15
Also, at section Setting up your VM:
To use the OS patch management service, you need to set up the OS
Config service API and install the OS Config agent. For detailed
instructions, see Managing your operating systems.
and as you can see at the documentation Managing your operating systems section Installing the OS Config agent there's no option for Google COS.
You can try to file a feature request at Google Issue Tracker if you need this feature.
below are the details of my OS(command ran :lsb_release -a)
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Amazon
Description: Amazon Linux release 2 (Karoo)
Release: 2
Codename: Karoo
When i'm trying to install the virtual6 getting the below errors(sudo dpkg -i virtualbox-6.1_6.1.4-136177_Ubuntu_bionic_amd64.deb)
dpkg: regarding virtualbox-6.1_6.1.4-136177_Ubuntu_bionic_amd64.deb containing virtualbox-6.1, pre-dependency problem:
**virtualbox-6.1 pre-depends on debconf (>= 1.1) | debconf-2.0
debconf is not installed.
debconf-2.0 is not installed.**
I installed the debconf(yum install debconf)
but still showing the same error as above ,am i missing something?
From: AWS Forum > Can you run VirtualBox/VMWare inside Amazon Workspaces
WorkSpaces are virtual machines themselves, they are unable to run or serve as a hypervisor. Unfortunately, at the moment, WorkSpaces does not support nested virtualization. That said, I would suggest you to try using Bare Metal EC2 instances, which allow full access to the underlying hardware. This would allow you to run your own hypervisor or emulation software.
When attempting to create a VM on EC2 with an Ubuntu 16.04 AMI ami-835b4efa, I see the following:
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded
This issue goes away if I create a VM using Ubuntu 14.04 with AMI ami-fc4f5e85. I've seen this in the past and thought it was just a fluke. It's happened enough times today repeatedly that I'm thinking there's some issue here. Any thoughts on why the above fails with Ubuntu 16.04? I can use 14.04 for now but would like to upgrade in the not too distant future and still use Docker Machine for managing my VMs.
I downloaded the latest version of Docker Toolbox for OSX today to take that off the table as a possible issue.
Check if this is similar to issue 2533 where:
What worked for me was adding a --amazonec2-ami param and setting it to
aws's Ubuntu 14.04 LTS image: ami-fce3c696
Since you are usiing Ubuntu 16.04, check the Amazon EC2 AMI Locator to try a similar option with the right AMI. It can depend on your region.
what version of docker and docker-machine? Whats in the logs on the machine? If docker-machine version 0.12.0, build 45c69ad and docker version 17.06.0-ce then its probably this issue in docker-machine: https://github.com/docker/machine/issues/4156
I need ubuntu 12.04 for my cloudera manager to install.It can't be installed on 14.04.So how can I choose the older version of ubuntu in mt ec2 instance?
Go to: Ubuntu AMI Finder
Scroll All the way to bottom of the page. Select version as 12.04. Select region and it will return a list of AMIs
This version of Ubuntu Server 12.04 LTS is not available to new customers.
So you need to see the compatibility for your required software under 14.04. Check the support forums since people would have surely moved on.