-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OLD docker] untergeek/curator missing signature key
on server
#1674
Comments
I can't do that. It's not that I'm being dogmatic about it so much as the requirement to make and release both amd64 and arm64 packages in the same manifest requires me to use much newer versions. My Docker build process won't even build on 20.10.23 (see #1672) leave alone 1.13.1 or I would recommend doing the Docker build yourself and pushing to your own local repository. I'd be happy to coach you through a few edits to the Dockerfile so you can build your own using 1.13.1 if you like. Even that process is tuned for multi-architecture builds and will not work out of the box with 1.13.1. |
I understand. With this issue others can at least find the reason for it, and the decision behind it. I'll be AFK for a couple of weeks now but I'm very interested in building since we won't be sunsetting that solution anytime soon. Should we follow up in this issue? |
Indeed. Any solution we can provide here will be of use to anyone else in the same situation. |
Linking the Dockerfile here: https://github.com/elastic/curator/blob/master/Dockerfile Would one need to fork your repo with the appropriate changes to |
I will likely create a gist that you can use as a drop in replacement to start. |
Did you get around to doing that gist? |
I have been out of office for family matters for most of the time we've been discussing this. I haven't had a chance yet. |
https://gist.github.com/untergeek/00dcb3f64cb0afa2f8fd194e9a5856d2 I can build and run Curator as a Docker image now in RHEL 7.9. I tested against an instance in Elastic Cloud and it works. That said, it is not a painless process, nor a quick fix. Caveats include:
|
Note that the addition of OpenSSL 1.1.1t will not impact the rest of the system as I chose to install it at |
missing signature key
on servermissing signature key
on server
I have encountered the same problem, and I solved it by remove the old version Docker provided by CentOS 7's Default Repository and installed a new version of Docker [root@ip-xxx]# cat /etc/redhat-release # docker version Client: Server: # docker build -t hello-world-nginx . Sending build context to Docker daemon 3.072 kB # yum remove docker \
docker-client \
docker-client-latest \
docker-common \
docker-latest \
docker-latest-logrotate \
docker-logrotate \
docker-engine
# yum install -y yum-utils
# yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
# yum install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
# systemctl restart docker.service # docker version Client: Docker Engine - Community Server: Docker Engine - Community Then docker pull works! # docker build -t hello-world-nginx . [+] Building 2.2s (7/7) FINISHED docker:default |
Expected Behavior
That
docker run untergeek/curator
should start curator.Actual Behavior
On RedHat Enterprise Linux 7 (RHEL7) getting the curator docker image fails:
Command:
output:
Unable to find image 'untergeek/curator:8.0.3' locally Trying to pull repository untergeek/curator ... /usr/bin/docker-current: missing signature key.
Running the same on i.e. Ubuntu 22.04 LTS works as expected, so I expect that it is an issue with the version of RHEL7 docker.
Steps to Reproduce the Problem
Specifications
Red Hat Enterprise Linux Server release 7.9 (Maipo)
Docker version, is the bundled docker version for RHEL7
Context (Environment)
One of our elasticsearch / kibana / logstash (ELK) platforms runs on RHEL7, and we use (used) curator to manage indices.
Since the upgrade to ELK-8 curator has not worked with the old version of curator.
Detailed Description
It would be great if the docker build could support all major versions of the underlying docker client / server versions.
The text was updated successfully, but these errors were encountered: