You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The official Nix Container Image cannot be used in Bitbucket Pipelines because Bitbucket requires the binaries /bin/echo/bin/cat and /usr/bin/mkfifo to be there in the image.
That of course does not make any sense, but even after reporting the issue to Bitbucket Bitbucket did not react and it seems this won't get fixed anytime soon.
Proposed solution
Instead of waiting & hoping for Bitbucket to fix this issue, we could propably update the Nix image to have these binaries symlinked accordingly. I don't like that we need to do this, but what's the point of having an official image if it doesn't run in all of the major build pipelines.
Alternative solutions
We could of course just wait for Bitbucket and let users create patched images for themselves (that's what we're doing currently).
Note: AFAIK there is no one currently maintaining anything related Docker in the Nix codebase. @garbas did that in the past, but the last activities were ~2 years ago IIRC.
Nix maintainers discussed this quite a while ago, and the gist is that if someone wants to take ownership of that, it would be greatly appreciated. I'd urge @nixos/nix-team to onboard new maintainers if the opportunity arises.
And also support to run the Nix cli tool as an random non-root userid without a $HOME would be great. The Gitlab CI in many larger companies runs inside restricted Openshift clusters. See #8074
Is your feature request related to a problem?
The official Nix Container Image cannot be used in Bitbucket Pipelines because Bitbucket requires the binaries
/bin/echo
/bin/cat
and/usr/bin/mkfifo
to be there in the image.That of course does not make any sense, but even after reporting the issue to Bitbucket Bitbucket did not react and it seems this won't get fixed anytime soon.
Proposed solution
Instead of waiting & hoping for Bitbucket to fix this issue, we could propably update the Nix image to have these binaries symlinked accordingly. I don't like that we need to do this, but what's the point of having an official image if it doesn't run in all of the major build pipelines.
Alternative solutions
We could of course just wait for Bitbucket and let users create patched images for themselves (that's what we're doing currently).
Additional context
There's also a topic on discourse about this: https://discourse.nixos.org/t/nixos-nix-docker-image-is-not-compatible-with-bitbucket-pipelines/48765
Checklist
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: