cloudfoundry / cloudfoundry/cli

can't load package : no Go files error while trying to upload and execute go binary on PCF

Open
#1,897 4 comments 0 reactions 1 assignee View on GitHub

@a-b is already working on this.

Since Oct 1, 2024.

unscheduled
Dominant language
Go
Stars
1.9k
Forks
990
Avg merge
1d 7h
Merged PRs (30d)
8

Description

Please fill out the issue checklist below and provide ALL the requested information.

  • I reviewed open and closed github issues that may be related to my problem.
  • I tried updating to the latest version of the CF CLI to see if it fixed my problem.
  • I attempted to run the command with CF_TRACE=1 to help debug the issue.
  • I am reporting a bug that others will be able to reproduce.
  • If this is an issue for the v7 beta release, I've read through the official docs and the release notes.

Describe the bug and the command you saw an issue with
I have been trying to upload go binary to pcf as we are planning to deploy it on PCF instead of VM.

What happened
While trying to use push command after login, its throwing invalid zip file error even when I have zipped that binary using tar -cvf command

Expected behavior
GO binary that we are planning to deploy on PCF should be uploaded to PCF successfully.

To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

  1. cf login
  2. cf push
    Pushing app .....
    Getting app info...
    zip: not a valid zip file
    FAILED

Provide more context

  • platform and shell details OEL 7.4 O.S.

  • version of the CLI you are running cf version 6.49.0+d0dfa93bb.2020-01-07, Cloud Foundry command line tool

  • version of the CC API Release you are on

Note: As of January 2019, we no longer support API versions older than CF Release v284/CF Deployment v1.7.0 (CAPI Release: 1.46.0 (APIs 2.100.0 and 3.35.0).

Note: In order to complete the v7 beta cf CLI in a timely matter, we develop and test against the latest CAPI release candidate. When v7 cf CLI is generally available, we will start supporting official CC API releases again.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.