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

Remove -c switch in call to nc of container backend #618

Closed
wants to merge 1 commit into from

Conversation

johbo
Copy link
Contributor

@johbo johbo commented Mar 9, 2017

Noticed that a call to "nixops ssh" did not work anymore after I upgraded the
target host to the current 17.03 channel.

Tracked the issue down to a change of the default netcat in the following PR:
NixOS/nixpkgs#19982

I've found the PR #559 which does seem to be wrong since -C (uppercase) has a different meaning than the -c from gnu-netcat.

Noticed that a call to "nixops ssh" did not work anymore after I upgraded the
target host to the current 17.03 channel.

Tracked the issue down to a change of the default netcat in the following PR:
NixOS/nixpkgs#19982
@RostakaGmfun
Copy link

That's a useful fix! Any chance for this to be merged?

@domenkozar
Copy link
Member

Can someone provide steps how to reproduce this?

@RostakaGmfun
Copy link

@domenkozar, here is an example configuration with a nixos-container running on the VirtualBox host:

{
  vbox =
    { deployment.targetEnv = "virtualbox";
      deployment.virtualbox.memorySize = 512;
      deployment.virtualbox.vcpu = 1;
      deployment.virtualbox.headless = true;
    };

  machine =
    { resources, ... }:
    { deployment.targetEnv = "container";
      deployment.container.host = resources.machines.vbox;
    };
}

The nixops ssh machine fails with the following error:

nc: invalid option -- 'c'
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
  [-P proxy_username] [-p source_port] [-q seconds] [-s source]
  [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
  [-x proxy_address[:port]] [destination] [port]
machine> could not connect to ‘root@192.168.56.101~10.233.1.2’, retrying in 1 seconds...

@johbo
Copy link
Contributor Author

johbo commented Jun 21, 2017

@RostakaGmfun yes, that's the same issue I was facing. I am currently full of work, cannot follow up that well in this PR at the moment.

@rbvermaa
Copy link
Member

rbvermaa commented Jul 24, 2017

d7411ed Testing without -c on netcat bsd and gnu seemed to work.

@rbvermaa rbvermaa closed this Jul 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants