While deploying docker using puppet, I encounter an interesting issue.
docker installs fine if I use: version => latest
docker install fails if I use: version => '20.10.16'
My setup is as follows:
puppet master is Ubuntu 20.04.
puppet agent is Ubuntu 22.04 (on which I am trying to install docker).
I believe puppet docker module supports this setup.
The version lines I tried:
version => '20.10.16'
version => '20.10.16~3-0~ubuntu'
version => '20.10.16~3-0~ubuntu-jammy'
The error I get when I specify a specific version is as follows:
Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install docker-ce=20.10.16' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
docker-ce-cli
Anyone has any idea what can be done so that it installs specific version of docker instead of the latest one?
When running apt-cache madison docker-ce it appears that the version number is 5:20.10.16~3-0~ubuntu-jammy.
Running apt install docker-ce=20.10.16~3-0~ubuntu-jammy returns the same error as yours, but apt install docker-ce=5:20.10.16~3-0~ubuntu-jammy works.
I suggest trying with the 5: in front of the version number.
Related
I download ROS Noetic but when I paste this line on Terminal, it can't found.
$ sudo apt-get install ros-indigo-ar-track-alvar
How can I solve this problem?
As I know, this package is avaliable for Noetic but I can't install it.
That command is trying to install the package for Indigo, not Noetic. Make sure your package names include the ROS distro you’re targeting.
sudo apt install ros-noetic-ar-track-alvar
Edit based on comment: It does appear there is a noetic build for this package, but it doesn't look like it's officially tracked on the ROS wiki. If it isn't supplied via apt you will need to build the package from source. The Noetic source can be found here on GitHub.
Im using electron which has already a production env running. For the last months I've been publishing normally with Electron-builder in my ci.yml file:
release-linux:
stage: release
image: electronuserland/builder:14
before_script:
- export ARCH="x64"
- export BUILD_SCRIPT="build:linux"
- apt-get update && apt-get install -y build-essential cmake
- apt install -y libusb-1.0-0-dev libudev-dev
After running the - apt-get update && apt-get install -y build-essential cmake line there is the libc6 package installed which installs with latest (2.35).
My production environment is running on Ubuntu 20.04 LTS. I assume the docker image in which the release is made, is running on a newer version (asuming latest).
The problem is that I have some hardware devices which works correctly with libc6=2.31-0ubuntu9.2 (which is the version that was automatically installed previously by the docker image). Now, for some reason I don't know, the image is pulling the latest version of libc6 and my hardware devices stoped working.
Is there any way to force electron-builder to use a specific Linux/Ubuntu version?
Or maybe use the latest version of ubuntu but downgrading the libc6 version (tried this one but failed). Any instructions on how to do this are apreciated.
Updating Ubuntu's version at production is not an option right now, so I think the solution should be working out with this package/library version.
The problem solved out on its own randomly, but after some research, it was a electron-builder change which was causing the problem.
In this commit changes log we can see that buildpack-deps was changed from buildpack-deps:22.04-curl (not working) to buildpack-deps:focal-curl (working).
That give us a clue to where to look at. Here the official supported tags for Dockerfiles. Here we can see that focal-curl points to 20.04-curl which I suppose have a different output than 20.04 by its own.
Then, looking at the gitlab jobs running with this ci configs, the libc6 dependency worked with different versions in each case.
Our hardware works correctly with libc6=2.31 which is used when focal-curl is set by electron-builder dockerfile, but not with libc6=2.35 which is used by 20.04.
This is not a solution, but it's the cause of the problem. Now working on how to setup the project to use only the correct configuration of electron-builder. Currently accepted to work with same config but being careful when releasing by watching which libc6 version is working with.
I have a Dockerfile that uses ruby:2.7.1-alpine base image. I have a gem that needs libcurl, which I am having troubles installing on the Alpine image. I saw a solution on a GitHub issue associate with the aforementioned gem. But that solution assumes a Debian-based OS, which mentions installing libcurl4-openssl-dev. What I need is the equivalent of this package on Alpine.
The equivalent package is curl-dev. Run:
apk add curl-dev
Source: See APT <-> APK packages table in this GitHub Issue.
I tried following this guide to install ROS, but even after adding ROS source.list and its key
sudo apt install ros-melodic-desktop-full
gave error.
E: Unable to locate package ros-melodic-desktop-full
Then I ran this command
sudo apt search ros
to see if any such package exists. I couldn't find ros-melodic-desktop-full but I found another similar package ros-desktop-full.
So I installed it instead. The installation went smooth without giving any errors.
Next step in the guide is to set-up ROS environment variable, but I have no such directory
/opt/ros
So how do I setup the environment variable?
P.S.
I also installed some tools and dependencies with this command
sudo apt install python3-rosdep python3-rosinstall python3-rosinstall-generator python3-wstool build-essential
and initialized rosdep
sudo rosdep init
rosdep update
The ros-desktop-full package you installed is part of the official Ubuntu release.
ROS Melodic (and in the future, Noetic) is published by the OSRF in a separate repository (packages.ros.org). These packages install to /opt/ros/. However, some ROS packages have also been ported to Debian, which is how they found their way to Ubuntu (which derives from Debian).
The Debian packages are fully functional, but they do not install to /opt/ros. Instead, everything is integrated in the operating system itself. This means that you need to set up your personal workspace slightly differently.
Given that most tutorials assume that you use the OSRF packages, I suggest you either wait for the Noetic release (scheduled for the end of May 2020), then install ros-noetic-desktop-full, or downgrade to Ubuntu 18.04 LTS to use ROS Melodic.
From the documentation here, melodic is only supported on Ubuntu 18.04. The ROS version targeting Focal (20.04) is Noetic, but that one has not been released yet (see Distributions). I'm not sure what ROS version Ubuntu packages (the ros-desktop-full one you installed), but I was not successful in using it.
If you really do want to use Ubuntu 20.04, then I think your best option currently is to compile from source. Last time I checked the precompiled debs for Noetic are not yet available at http://packages.ros.org/ros/ubuntu (you can track release progress at github issue 21513). No idea if compiling Noetic from source is easy or hard, but I was able to compile ROS2 foxy from source without too much trouble though.
I am installing Grails on Ubuntu 12.10, using the instructions here, but an getting an error on the 3rd step, as outlines below.
sudo add-apt-repository ppa:groovy-dev/grails
sudo apt-get update
sudo apt-get install grails-ppa
The error I get is shown below. I have the Sun JDK installed, and JAVA_HOME is set, and JAVA_HOME/bin is on the path.
Can someone suggest things to try to resolve this?
/home/edgecase> $ sudo apt-get install grails-ppa
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
default-jre-headless:i386 : Depends: openjdk-7-jre-headless:i386 (>= 7~u3-2.1) but it is not going to be installed
openjdk-7-jre:i386 : Depends: openjdk-7-jre-headless:i386 (= 7u7-2.3.2a-1ubuntu1) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
/home/edgecase> $ java -version
java version "1.6.0_39"
Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)
We need to remove those instructions from the site since the PPA isn't being maintained. Use http://gvmtool.net/ instead.
YES please remove the PPA instructions with GVM, I wasted a lot of time before I found this