Skip to content
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

Docker-In-Docker failure #11

Open
njdowdy opened this issue May 9, 2024 · 2 comments
Open

Docker-In-Docker failure #11

njdowdy opened this issue May 9, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@njdowdy
Copy link

njdowdy commented May 9, 2024

Description of the bug

This pipeline is not compatible with Docker-in-Docker using Docker version >=26 due to a deprecation of the schema that the BLAT image uses.

More info: https://docs.docker.com/engine/deprecated/#pushing-and-pulling-with-image-manifest-v2-schema-1

To my knowledge, the only fix is for the BLAT maintainer to update their image to meet the new standards or to pin the supported docker version to 25 or earlier.

Command used and terminal output

[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/feathj/fake-sqs:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/

Relevant files

No response

System information

No response

@njdowdy njdowdy added the bug Something isn't working label May 9, 2024
@IanGBrennan
Copy link
Contributor

Hey there, sorry for the slow reply on this.
Could you explain a bit more about why this might be important? I am not familiar with docker-in-docker usage, and so curious if this is something like to become an issue, or if it's a less common practice.
Cheers
Ian

@njdowdy
Copy link
Author

njdowdy commented May 16, 2024

I have an HPC that runs docker containers. I need to run the Nextflow environment in a docker container, which itself uses the PipeSnake docker container, necessitating the docker-in-docker nesting. To resolve the above issue, I pulled an image of Docker pinned to version 25, installed Nextflow within the container, and then continued with the PipeSnake installation instructions to get around the above problem. So, just a mild frustration.

The real "solution" is for the BLAT maintainer to maintain their Docker image or for PipeSnake to use an alternative BLAT image that follows Docker's new standards around Docker Image manifest/schema rules. I'm not sure if you all were interested in looking for an alternative BLAT image that conforms to these standards, or if this comment would simply serve as an FYI to the community in case they run into this problem too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants