-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d9ee385
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have noticed that the path to the snowplow application has been changed in this relase (used to be
ENTRYPOINT ["/opt/snowplow/bin/snowplow-stream-collector"]
and now it'sENTRYPOINT ["/home/snowplow/bin/snowplow-stream-collector"]
). It would be nice to have it explicitly included in the CHANGELOG to avoid confusion. We had problems in our pipeline before because of implicit path/folder structure changes because we have a complex setup where we need to load additional objects into the same directory as the snowplow app.d9ee385
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @piankris , may I ask what is your complex setup that prevents you from running the original Docker image that we publish ?
d9ee385
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We load config files into the directory where the snowplow app is launched, so the path is critical here. The change in the path prevents the snowplow app from finding the configs then and thus to start.
d9ee385
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not mounting the config files with
-v
directly in yourdocker run
command ? This way you wouldn't need to maintain your own imaged9ee385
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use docker compose for all the snowplow modules. While some images can be used as they are, in others we have to do minor changes like substituting environment variables with
sed
commands because some modules don't have support forhocon
configs. And of course, the shredder requires a little more work to set it up. Thus the necessity for custom images.