Skip to content

[Bug] Dockerfile does not build, does not line up with conf/rest-server.properties #2015

Closed

Description

@baughmann

Bug Type (问题类型)

other exception / error (其他异常报错)

Before submit

  • 我已经确认现有的 Issues 与 FAQ 中没有相同 / 重复问题

Environment (环境信息)

  • Server Version: v0.12.0
  • Backend: N/A
  • OS: Fedora 37 Workstation
  • Data Size: N/A

Expected & Actual behavior (期望与实际表现)

Expected

I should be able to clone this repo and run docker build . with no errors. Command should result in a built container.

Actual

See my comments on the commit associated with #1901

The sed line numbers referencing the server's default conf/rest-server.properties were updated for 0.12.0 but appears to still be off by one line. Simply changing it to 66p and 76p respectively allow me to build the container.

I would be happy to submit a PR for this simple fix, but wanted to make sure that I was in the right and that my problem was reproducible before doing so.

Vertex/Edge example (问题点 / 边数据举例)

N/A

Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

N/A

Activity

  1. imbajin commented on Nov 13, 2022

    @imbajin
    Member

    thanks for your report, @simon824 could u help to check it?

    we should use the latest code to build automatically (while release the first apache version 1.0.0)

    and sed is not a good way (due to the hard code), consider add a option (-fg to run not in background), and welcome to contribute & enhance it (could refer this issue to see the TODOs #840 )

  2. simon824 commented on Nov 14, 2022

    @simon824
    Member

    Hi @baughmann ,refer to v0.12.0-b1, you can change it to 66p and 76p, but as @imbajin said, sed is not a good way, maybe you can improve it if you are interested.

  3. baughmann commented on Nov 15, 2022

    @baughmann
    Author

    @imbajin @simon824 Thanks for getting back to me, guys.

    I am not yet sure when I can get around to it. I know I just said two days ago that I would be happy to submit a PR, but a few things have changed on my end since. Turns out we will no longer be using HugeGraph (at least for now...)

    Best I can hope to do is through another bash hack in there, but please don't wait on me :(

    Were you able to replicate this behavior on your end, Simon?

  4. simon824 commented on Nov 15, 2022

    @simon824
    Member

    ok, good luck @baughmann

  5. baughmann commented on Nov 17, 2022

    @baughmann
    Author

    @simon824 Just to reiterate this is not something I'm actively working on, unfortunately.

    Were you able to replicate the bug, or is it just me?

  6. imbajin commented on Nov 22, 2022

    @imbajin
    Member

    @simon824 Just to reiterate this is not something I'm actively working on, unfortunately.

    Were you able to replicate the bug, or is it just me?

    I'll address this issue soon, and push a stable version to Dockerhub or Apache's image repo

  7. imbajin commented on Nov 29, 2022

    @imbajin
    Member

    Update:

    I do can repeat this problem, maybe the download link 0.12 is not related with the branch 0.12 (maybe with 0.12-xx)

    And I will update the script & use the latest code to avoid hard code the line, thanks @baughmann for report it

  8. imbajin commented on Mar 17, 2023

    @imbajin
    Member

    This problem fixed in #2118, and we update the usage doc in README & Dockerhub for users

    Thanks for the report again. (Docker TODOs summary in issue $840)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions